blocks|key|1491539|text|可以在requirements.txt中使用“Editable”+packages+syntax从各种VCS+(git,+hg,+bzr,+svn)导入包|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1491540|-e+git://github.com/mozilla/elasticutils.git#egg=elasticutils|code-block|syntax|javascript|1491541|此外，还可以指向特定的提交：|1491542|-e+git://github.com/mozilla/elasticutils.git@000b14389171a9f0d7d713466b32bc649b0bed8e#egg=elasticutils|1491543|entityMap|0|LINK|mutability|MUTABLE|url|https://pip.pypa.io/en/stable/cli/pip_install/#install-editable|1|https://pip.readthedocs.org/en/1.1/requirements.html#version-control^0|3|G|M|Q|0|1F|N|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]]|D|@$9|11|A|12|1|13]|$9|14|A|15|1|16]]|E|$]]|$1|F|3|G|5|H|7|17|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|18|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|19|8|@]|D|@]|E|$I|J]]|$1|O|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]]|P|$Q|$5|R|S|T|E|$U|V]]|W|$5|R|S|T|E|$U|X]]]]

<a href="https://pip.pypa.io/en/stable/cli/pip_install/#install-editable" rel="noreferrer">“Editable” packages syntax</a> can be used in <code>requirements.txt</code> to import packages from a variety of <a href="https://pip.readthedocs.org/en/1.1/requirements.html#version-control" rel="noreferrer">VCS (git, hg, bzr, svn)</a>:
<pre><code>-e git://github.com/mozilla/elasticutils.git#egg=elasticutils
</code></pre>
Also, it is possible to point to particular commit:
<pre><code>-e git://github.com/mozilla/elasticutils.git@000b14389171a9f0d7d713466b32bc649b0bed8e#egg=elasticutils
</code></pre>

blocks|key|348456|text|首先，以您所知道的任何方式安装git%2Bgit或git%2Bhttps。安装brabeion项目的kronok分支的示例：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|348457|pip+install+-e+git%2Bhttps://github.com/kronok/brabeion.git@12efe6aa06b85ae5ff725d3033e38f624e0a616f#egg=brabeion|code-block|syntax|javascript|348458|其次，在您的requirements.txt中使用pip+freeze+>+requirements.txt获取正确的内容。在这种情况下，您将获得|348459|-e+git%2Bhttps://github.com/kronok/brabeion.git@12efe6aa06b85ae5ff725d3033e38f624e0a616f#egg=brabeion-master|348460|第三，测试结果：|348461|pip+uninstall+brabeion
pip+install+-r+requirements.txt|348462|entityMap^0|F|7|N|9|Z|8|1A|6|0|0|6|G|P|T|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]|$9|11|A|12|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|13|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|14|8|@$9|15|A|16|B|C]|$9|17|A|18|B|C]]|D|@]|E|$]]|$1|M|3|N|5|H|7|19|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|1A|8|@]|D|@]|E|$]]|$1|Q|3|R|5|H|7|1B|8|@]|D|@]|E|$I|J]]|$1|S|3|-4|5|6|7|1C|8|@]|D|@]|E|$]]]|T|$]]

First, install with <code>git+git</code> or <code>git+https</code>, in any way you know. Example of installing <code>kronok</code>'s branch of the <code>brabeion</code> project:

<pre><code>pip install -e git+https://github.com/kronok/brabeion.git@12efe6aa06b85ae5ff725d3033e38f624e0a616f#egg=brabeion
</code></pre>

Second, use <code>pip freeze &gt; requirements.txt</code> to get the right thing in your <code>requirements.txt</code>. In this case, you will get

<pre><code>-e git+https://github.com/kronok/brabeion.git@12efe6aa06b85ae5ff725d3033e38f624e0a616f#egg=brabeion-master
</code></pre>

Third, test the result:

<pre><code>pip uninstall brabeion
pip install -r requirements.txt
</code></pre>

blocks|key|1488943|text|自pip+v1.5+(2014年1月1日发布：CHANGELOG，PR)以来，您还可以指定git代码库的子目录来包含您的模块。语法如下所示：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1488944|pip+install+-e+git%2Bhttps://git.repo/some_repo.git#egg=my_subdir_pkg&subdirectory=my_subdir_pkg+#+install+a+python+package+from+a+repo+subdirectory|code-block|syntax|javascript|1488945|注意:作为pip模块的作者，理想情况下，如果可以的话，您可能希望在它自己的顶级存储库中发布您的模块。然而，这个特性对于在子目录中包含python模块的一些预先存在的repos很有帮助。如果它们没有发布到pypi，你可能会被迫以这种方式安装。|1488946|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/pypa/pip/blob/develop/CHANGES.txt|1|https://github.com/pypa/pip/pull/1215^0|5|4|N|9|0|X|2|1|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@$9|Z|A|10|1|11]|$9|12|A|13|1|14]]|E|$]]|$1|F|3|G|5|H|7|15|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|16|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|17|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]|U|$5|P|Q|R|E|$S|V]]]]

Since pip <code>v1.5</code>, (released Jan 1 2014: <a href="https://github.com/pypa/pip/blob/develop/CHANGES.txt" rel="noreferrer">CHANGELOG</a>, <a href="https://github.com/pypa/pip/pull/1215" rel="noreferrer">PR</a>) you may also specify a subdirectory of a git repo to contain your module. The syntax looks like this:

<pre><code>pip install -e git+https://git.repo/some_repo.git#egg=my_subdir_pkg&amp;subdirectory=my_subdir_pkg # install a python package from a repo subdirectory
</code></pre>

Note: As a pip module author, ideally you'd probably want to publish your module in it's own top-level repo if you can. Yet this feature is helpful for some pre-existing repos that contain python modules in subdirectories. You might be forced to install them this way if they are not published to pypi too.

blocks|key|1331738|text|通常情况下，您的requirements.txt文件如下所示：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1331739|package-one==1.9.4
package-two==3.7.1
package-three==1.0.1
...|code-block|syntax|javascript|1331740|要指定Github存储库，您不需要package-name==约定。|1331741|下面的示例使用GitHub存储库更新package-two。@和#之间的文本表示包的细节。|1331742|指定提交哈希(在更新的requirements.txt上下文中为41b95ec)：|1331743|package-one==1.9.4
git%2Bgit://github.com/path/to/package-two@41b95ec#egg=package-two
package-three==1.0.1|1331744|指定分支名称(master)：|1331745|git%2Bgit://github.com/path/to/package-two@master#egg=package-two|1331746|指定标签(0.1)：|1331747|git%2Bgit://github.com/path/to/package-two@0.1#egg=package-two|1331748|指定版本(3.7.1)：|1331749|git%2Bgit://github.com/path/to/package-two@releases/tag/v3.7.1#egg=package-two|1331750|请注意，#egg=package-two在这里不是注释，它是针对explicitly+state+the+package+name的|1331751|This+blog+post在这个话题上有更多的讨论。|1331752|entityMap|0|LINK|mutability|MUTABLE|url|https://pip.pypa.io/en/stable/reference/pip_install/#working-out-the-name-and-version|1|http://codeinthehole.com/writing/using-pip-and-requirementstxt-to-install-from-the-head-of-a-github-branch/^0|8|G|0|0|H|E|0|I|B|U|1|W|1|0|B|G|W|7|0|0|7|6|0|0|5|3|0|0|5|5|0|0|4|G|W|X|0|0|0|E|1|0^^$0|@$1|2|3|4|5|6|7|1I|8|@$9|1J|A|1K|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|1L|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|1M|8|@$9|1N|A|1O|B|C]]|D|@]|E|$]]|$1|M|3|N|5|6|7|1P|8|@$9|1Q|A|1R|B|C]|$9|1S|A|1T|B|C]|$9|1U|A|1V|B|C]]|D|@]|E|$]]|$1|O|3|P|5|6|7|1W|8|@$9|1X|A|1Y|B|C]|$9|1Z|A|20|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|H|7|21|8|@]|D|@]|E|$I|J]]|$1|S|3|T|5|6|7|22|8|@$9|23|A|24|B|C]]|D|@]|E|$]]|$1|U|3|V|5|H|7|25|8|@]|D|@]|E|$I|J]]|$1|W|3|X|5|6|7|26|8|@$9|27|A|28|B|C]]|D|@]|E|$]]|$1|Y|3|Z|5|H|7|29|8|@]|D|@]|E|$I|J]]|$1|10|3|11|5|6|7|2A|8|@$9|2B|A|2C|B|C]]|D|@]|E|$]]|$1|12|3|13|5|H|7|2D|8|@]|D|@]|E|$I|J]]|$1|14|3|15|5|6|7|2E|8|@$9|2F|A|2G|B|C]]|D|@$9|2H|A|2I|1|2J]]|E|$]]|$1|16|3|17|5|6|7|2K|8|@]|D|@$9|2L|A|2M|1|2N]]|E|$]]|$1|18|3|-4|5|6|7|2O|8|@]|D|@]|E|$]]]|19|$1A|$5|1B|1C|1D|E|$1E|1F]]|1G|$5|1B|1C|1D|E|$1E|1H]]]]

Normally your <code>requirements.txt</code> file would look something like this:

<pre><code>package-one==1.9.4
package-two==3.7.1
package-three==1.0.1
...
</code></pre>

To specify a Github repo, you do not need the <code>package-name==</code> convention. 

The examples below update <code>package-two</code> using a GitHub repo. The text between <code>@</code> and <code>#</code> denotes the specifics of the package.

<h2>Specify commit hash (<code>41b95ec</code> in the context of updated <code>requirements.txt</code>):</h2>

<pre><code>package-one==1.9.4
git+git://github.com/path/to/package-two@41b95ec#egg=package-two
package-three==1.0.1
</code></pre>

<h2>Specify branch name (<code>master</code>):</h2>

<pre><code>git+git://github.com/path/to/package-two@master#egg=package-two
</code></pre>

<h2>Specify tag (<code>0.1</code>):</h2>

<pre><code>git+git://github.com/path/to/package-two@0.1#egg=package-two
</code></pre>

<h2>Specify release (<code>3.7.1</code>):</h2>

<pre><code>git+git://github.com/path/to/package-two@releases/tag/v3.7.1#egg=package-two
</code></pre>

Note that <code>#egg=package-two</code> is not a comment here, it is to <a href="https://pip.pypa.io/en/stable/reference/pip_install/#working-out-the-name-and-version" rel="noreferrer">explicitly state the package name</a>

<a href="http://codeinthehole.com/writing/using-pip-and-requirementstxt-to-install-from-the-head-of-a-github-branch/" rel="noreferrer">This blog post</a> has some more discussion on the topic.

blocks|key|1491625|text|我发现让pip3+(v9.0.1，由Ubuntu18.04的包管理器安装)实际安装我告诉它要安装的东西有点棘手。我发布这个答案是为了节省遇到这个问题的任何人的时间。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1491626|将此文件放入requirements.txt文件失败：|1491627|git%2Bgit://github.com/myname/myrepo.git@my-branch#egg=eggname|code-block|syntax|javascript|1491628|所谓“失败”，我的意思是，虽然它从Git下载了代码，但它最终安装的是PyPi上的原始代码版本，而不是该分支上的存储库中的代码。|1491629|但是，安装commmit而不是分支名称是可行的：|1491630|git%2Bgit://github.com/myname/myrepo.git@d27d07c9e862feb939e56d0df19d5733ea7b4f4d#egg=eggname|1491631|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|F|7|V|8|@]|9|@]|A|$G|H]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

I'm finding that it's kind of tricky to get pip3 (v9.0.1, as installed by Ubuntu 18.04's package manager) to actually install the thing I tell it to install. I'm posting this answer to save anyone's time who runs into this problem.

Putting this into a requirements.txt file failed:

<pre><code>git+git://github.com/myname/myrepo.git@my-branch#egg=eggname
</code></pre>

By "failed" I mean that while it downloaded the code from Git, it ended up installing the original version of the code, as found on PyPi, instead of the code in the repo on that branch.

However, installing the commmit instead of the branch name works:

<pre><code>git+git://github.com/myname/myrepo.git@d27d07c9e862feb939e56d0df19d5733ea7b4f4d#egg=eggname
</code></pre>

blocks|key|3457134|text|Github的zip端点在我看来比使用git协议更可取。它的优势是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3457135|#egg=<project+name>|offset|length|style|CODE|3457136|Git不需要在您的环境中安装，这对于容器化的environments|unordered-list-item|3457137|
|3457138|It来说很好，它可以更好地与pip+hashing和|3457139|3457140|配合使用URL结构更容易记住，并且更具discoverable|3457141|3457142|您通常希望requirements.txt条目如下所示，例如，不带-e前缀：|3457143|https://github.com/org/package/archive/1a58aa586efd4bca37f2cfb9d9348958986aab6c.tar.gz|code-block|syntax|javascript|3457144|要从主分支安装：|3457145|https://github.com/org/package/archive/main.tar.gz|3457146|还有一个等效的unicode端点，但在注释中报告说，始终使用.zip端点可以避免出现.tar.gz包名的问题。|3457147|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/jazzband/pip-tools#using-hashes^0|0|0|J|0|0|0|E|B|0|0|0|0|0|X|2|0|0|0|0|U|4|16|7|0^^$0|@$1|2|3|4|5|6|7|1D|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1E|8|@$D|1F|E|1G|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|1H|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|1I|8|@]|9|@]|A|$]]|$1|M|3|N|5|J|7|1J|8|@]|9|@$D|1K|E|1L|1|1M]]|A|$]]|$1|O|3|L|5|6|7|1N|8|@]|9|@]|A|$]]|$1|P|3|Q|5|J|7|1O|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1P|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1Q|8|@$D|1R|E|1S|F|G]]|9|@]|A|$]]|$1|U|3|V|5|W|7|1T|8|@]|9|@]|A|$X|Y]]|$1|Z|3|10|5|6|7|1U|8|@]|9|@]|A|$]]|$1|11|3|12|5|W|7|1V|8|@]|9|@]|A|$X|Y]]|$1|13|3|14|5|6|7|1W|8|@$D|1X|E|1Y|F|G]|$D|1Z|E|20|F|G]]|9|@]|A|$]]|$1|15|3|-4|5|6|7|21|8|@]|9|@]|A|$]]]|16|$17|$5|18|19|1A|A|$1B|1C]]]]

Github has zip endpoints that in my opinion are preferable to using the git protocol. The advantages are:
<ul>
<li>You don't have to specify <code>#egg=&lt;project name&gt;</code></li>
<li>Git doesn't need to be installed in your environment, which is nice for containerized environments</li>
<li>It works much better with <a href="https://github.com/jazzband/pip-tools#using-hashes" rel="nofollow noreferrer">pip hashing</a> and caching</li>
<li>The URL structure is easier to remember and more discoverable</li>
</ul>
You usually want requirements.txt entries to look like this, e.g. without the <code>-e</code> prefix:
<pre><code>https://github.com/org/package/archive/1a58aa586efd4bca37f2cfb9d9348958986aab6c.tar.gz
</code></pre>
To install from main branch:
<pre><code>https://github.com/org/package/archive/main.tar.gz
</code></pre>
There is also an equivalent <code>.zip</code> endpoint, but it was reported in a comment that always using the <code>.tar.gz</code> endpoint avoids problems with unicode package names.

blocks|key|3457180|text|看起来这也是一种有效的格式：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3457181|gym-tictactoe+@+git%2Bhttps://github.com/haje01/gym-tictactoe.git@84e22fc28fe192ba0040bdd56a697f63d3d4a3d5|code-block|syntax|javascript|3457182|如果您执行pip+install+"git%2Bhttps://github.com/haje01/gym-tictactoe.git"，然后查看通过运行pip+freeze安装的内容，您将看到以这种格式描述的包，并且可以复制并粘贴到requirements.txt中。|offset|length|style|CODE|3457183|entityMap^0|0|0|5|1P|23|A|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]|$I|T|J|U|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|N|$]]

It seems like this is also a valid format:
<pre><code>gym-tictactoe @ git+https://github.com/haje01/gym-tictactoe.git@84e22fc28fe192ba0040bdd56a697f63d3d4a3d5
</code></pre>
If you do a <code>pip install &quot;git+https://github.com/haje01/gym-tictactoe.git&quot;</code>, then look at what got installed by running <code>pip freeze</code>, you will see the package described in this format and can copy and paste into requirements.txt.

blocks|key|348537|text|这些答案对我来说都不起作用。唯一有效的方法是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|348538|git%2Bhttps://github.com/path_to_my_project.git|code-block|syntax|javascript|348539|没有"e"，没有两个"git“，也不需要以前的安装。|348540|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

None of these answers worked for me. The only thing that worked was:
<pre><code>git+https://github.com/path_to_my_project.git
</code></pre>
No &quot;e&quot;, no double &quot;git&quot; and no previous installs necessary.

blocks|key|1491678|text|对于私有存储库，我发现这两个对我来说很好：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1491679|pip+install+https://${GITHUB_TOKEN}@github.com/owner/repo/archive/main.tar.gz|code-block|syntax|javascript|1491680|其中main.tar.gz指的是存储库的main分支，可以替换为其他分支名称。有关更多信息以及如何使用最新的Github+API，请参阅here|offset|length|style|CODE|1491681|pip+install+https://${GITHUB_TOKEN}@api.github.com/repos/owner/repo/tarball/master|1491682|如果您已经安装了git并可用，那么|1491683|pip+install+git%2Bhttps://${GITHUB_TOKEN}@github.com/owner/repo.git@main|1491684|实现了同样的功能，而且它还允许通过附加@branch、@tag或@commit-hash来实现更大的灵活性。然而，这种方法实际上会将存储库克隆到本地临时文件夹中，这可能会花费大量的时间。|1491685|您也可以在requirements.txt中使用这些URL。|1491686|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.github.com/en/rest/reference/repos#download-a-repository-archive-tar^0|0|0|2|B|K|4|1W|4|0|0|0|0|0|J|7|R|4|W|C|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|15|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|16|8|@$I|17|J|18|K|L]|$I|19|J|1A|K|L]]|9|@$I|1B|J|1C|1|1D]]|A|$]]|$1|M|3|N|5|D|7|1E|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|1F|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|1G|8|@]|9|@]|A|$E|F]]|$1|S|3|T|5|6|7|1H|8|@$I|1I|J|1J|K|L]|$I|1K|J|1L|K|L]|$I|1M|J|1N|K|L]]|9|@]|A|$]]|$1|U|3|V|5|6|7|1O|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1P|8|@]|9|@]|A|$]]]|X|$Y|$5|Z|10|11|A|$12|13]]]]

For private repositories, I found that these two work fine for me:
<pre><code>pip install https://${GITHUB_TOKEN}@github.com/owner/repo/archive/main.tar.gz
</code></pre>
Where <code>main.tar.gz</code> refers to the <code>main</code> branch of your repo and can be replaced with other branch names. For more information and using the more recent Github API see <a href="https://docs.github.com/en/rest/reference/repos#download-a-repository-archive-tar" rel="nofollow noreferrer">here</a>:
<pre><code>pip install https://${GITHUB_TOKEN}@api.github.com/repos/owner/repo/tarball/master
</code></pre>
If you have git installed and available, then
<pre><code>pip install git+https://${GITHUB_TOKEN}@github.com/owner/repo.git@main
</code></pre>
achieves the same, and it also allows for some more flexibility by appending <code>@branch</code> or <code>@tag</code> or <code>@commit-hash</code>. That approach, however, actually clones the repo into a local temp folder which can take a noticeable amount of time.
You can use the URLs in your requirements.txt, too.

I've installed a library using the command
<pre><code>pip install git+git://github.com/mozilla/elasticutils.git
</code></pre>
which installs it directly from a Github repository. This works fine and I want to have that dependency in my <code>requirements.txt</code>. I've looked at other tickets like <a href="https://stackoverflow.com/questions/9024607/how-to-link-to-forked-package-in-distutils-without-breaking-pip-freeze">this</a> but that didn't solve my problem. If I put something like
<pre><code>-f git+git://github.com/mozilla/elasticutils.git
elasticutils==0.7.dev
</code></pre>
in the <code>requirements.txt</code> file, a <code>pip install -r requirements.txt</code> results in the following output:
<pre><code>Downloading/unpacking elasticutils==0.7.dev (from -r requirements.txt (line 20))
 Could not find a version that satisfies the requirement elasticutils==0.7.dev (from -r requirements.txt (line 20)) (from versions: )
No distributions matching the version for elasticutils==0.7.dev (from -r requirements.txt (line 20))
</code></pre>
The <a href="https://pip.pypa.io/en/stable/reference/pip_install/#requirements-file-format" rel="noreferrer">documentation of the requirements file</a> does not mention links using the <code>git+git</code> protocol specifier, so maybe this is just not supported.
Does anybody have a solution for my problem?

How to state in requirements.txt a direct github source

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

我已经使用以下命令安装库pip install git+git://github.com/mozilla/elasticutils.git它直接从Github存储库安装。这很好用，我希望在我的requirements.txt中有那个依赖项。我已经看过像这样的其他票据，但这并没有解决我的问题。如果我把像这样的东西-f g...

问如何在requirements.txt中声明一个直接的github源代码
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在requirements.txt中声明一个直接的github源代码EN