How to state in requirements.txt a direct github source

Each Answer to this Q is separated by one/two green lines.

I’ve installed a library using the command

pip install git+git://

which installs it directly from a Github repository. This works fine and I want to have that dependency in my requirements.txt. I’ve looked at other tickets like this but that didn’t solve my problem. If I put something like

-f git+git://

in the requirements.txt file, a pip install -r requirements.txt results in the following output:

Downloading/unpacking (from -r requirements.txt (line 20))
  Could not find a version that satisfies the requirement (from -r requirements.txt (line 20)) (from versions: )
No distributions matching the version for (from -r requirements.txt (line 20))

The documentation of the requirements file does not mention links using the git+git protocol specifier, so maybe this is just not supported.

Does anybody have a solution for my problem?

Normally your requirements.txt file would look something like this:


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

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

Specify commit hash (41b95ec in the context of updated requirements.txt):

git+[email protected]#egg=package-two

Specify branch name (master):

git+[email protected]#egg=package-two

Specify tag (0.1):

git+[email protected]#egg=package-two

Specify release (3.7.1):

git+[email protected]/tag/v3.7.1#egg=package-two

Note that #egg=package-two is not a comment here, it is to explicitly state the package name

This blog post has some more discussion on the topic.

“Editable” packages syntax can be used in requirements.txt to import packages from a variety of VCS (git, hg, bzr, svn):

-e git://

Also, it is possible to point to particular commit:

-e git://[email protected]#egg=elasticutils

requirements.txt allows the following ways of specifying a dependency on a package in a git repository as of pip 7.0:1

[-e] git+git://
[-e] git+
[-e] git+ssh://
-e [email protected]:SomeProject#egg=SomeProject (deprecated as of Jan 2020)

For Github that means you can do (notice the omitted -e):


Why the extra answer?
I got somewhat confused by the -e flag in the other answers so here’s my clarification:

The -e or --editable flag means that the package is installed in <venv path>/src/SomeProject and thus not in the deeply buried <venv path>/lib/pythonX.X/site-packages/SomeProject it would otherwise be placed in.2


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

pip install -e git+[email protected]#egg=brabeion

Second, use pip freeze > requirements.txt to get the right thing in your requirements.txt. In this case, you will get

-e git+[email protected]#egg=brabeion-master

Third, test the result:

pip uninstall brabeion
pip install -r requirements.txt

Since pip v1.5, (released Jan 1 2014: CHANGELOG, PR) you may also specify a subdirectory of a git repo to contain your module. The syntax looks like this:

pip install -e git+https://git.repo/some_repo.git#egg=my_subdir_pkg&subdirectory=my_subdir_pkg # install a python package from a repo subdirectory

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.

Github has zip endpoints that in my opinion are preferable to using the git protocol. The advantages are:

  • You don’t have to specify #egg=<project name>
  • Git doesn’t need to be installed in your environment, which is nice for containerized environments
  • It works much better with pip hashing and caching
  • The URL structure is easier to remember and more discoverable

You usually want requirements.txt entries to look like this, e.g. without the -e prefix:

To install from main branch:

There is also an equivalent .zip endpoint, but it was reported in a comment that always using the .tar.gz endpoint avoids problems with unicode package names.

None of these answers worked for me. The only thing that worked was:


No “e”, no double “git” and no previous installs necessary.

It seems like this is also a valid format:

gym-tictactoe @ git+[email protected]

If you do a pip install "git+", then look at what got installed by running pip freeze, you will see the package described in this format and can copy and paste into requirements.txt.

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:

git+git://[email protected]#egg=eggname

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:

git+git://[email protected]#egg=eggname

For private repositories, I found that these two work fine for me:

pip install https://${GITHUB_TOKEN}

Where main.tar.gz refers to the main branch of your repo and can be replaced with other branch names. For more information and using the more recent Github API see here:

pip install https://${GITHUB_TOKEN}

If you have git installed and available, then

pip install git+https://${GITHUB_TOKEN}[email protected]

achieves the same, and it also allows for some more flexibility by appending @branch or @tag or @commit-hash. 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.

The answers/resolutions are collected from stackoverflow, are licensed under cc by-sa 2.5 , cc by-sa 3.0 and cc by-sa 4.0 .

Leave a Reply

Your email address will not be published.