Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

pip requires the "-e" option to install from a scheme that starts with "git+git@"

See original GitHub issue

Looks like it’s not recognized and passed further into pkg_resources:

Exception:
Traceback (most recent call last):
  File "/usr/local/lib/python3.4/site-packages/pip/basecommand.py", line 223, in main
    status = self.run(options, args)
  File "/usr/local/lib/python3.4/site-packages/pip/commands/install.py", line 270, in run
    wheel_cache
  File "/usr/local/lib/python3.4/site-packages/pip/basecommand.py", line 275, in populate_requirement_set
    wheel_cache=wheel_cache
  File "/usr/local/lib/python3.4/site-packages/pip/req/req_install.py", line 212, in from_line
    wheel_cache=wheel_cache, constraint=constraint)
  File "/usr/local/lib/python3.4/site-packages/pip/req/req_install.py", line 66, in __init__
    req = pkg_resources.Requirement.parse(req)
  File "/usr/local/lib/python3.4/site-packages/pip/_vendor/pkg_resources/__init__.py", line 2980, in parse
    reqs = list(parse_requirements(s))
  File "/usr/local/lib/python3.4/site-packages/pip/_vendor/pkg_resources/__init__.py", line 2924, in parse_requirements
    "version spec")
  File "/usr/local/lib/python3.4/site-packages/pip/_vendor/pkg_resources/__init__.py", line 2889, in scan_list
    raise RequirementParseError(msg, line, "at", line[p:])
pip._vendor.pkg_resources.RequirementParseError: Expected version spec in git+git@github.com:My/repo.git@master#egg=repo at +git@github.com:My/repo.git@master#egg=repo

Issue Analytics

State:
Created 8 years ago
Comments:17 (9 by maintainers)

Top GitHub Comments

1reaction

sbidoulcommented, Jan 4, 2020

Closing as we propose to remove the git+git@ form in #7554.

1reaction

shelldwellercommented, Feb 14, 2019

I see. Thanks @xavfernandez. The confusion (at least for me) comes from the differences in URL format: git+ssh://git@github.com/user works but git+ssh://git@github.com:user doesn’t. Interestingly all major VCS providers (Github, Bitbucket, GitLab) give you SSH clone URL in the latter format. It is not obvious at all that one has to tweak the URL for it to work in non-editable mode.

Top Results From Across the Web

Is it possible to use pip to install a package from a private ...

You can use the git+ssh URI scheme, but you must set a username. Notice the git@ part in the URI: pip install git+ssh://git@github.com/echweb/echweb-utils....

PIP Install Git - A quick read - ActiveState

By default, pip installs packages and all their required dependencies from the Python Package Index (PyPI), using the command: pip install < ...

VCS Support - pip documentation v22.3.1

pip supports installing from various version control systems (VCS). This support requires a working executable to be available (for the version control ...

pip install — pip 8.1.1 documentation

pip requires a working VCS command on your path: git, hg, svn, or bzr. VCS projects can be installed in editable mode (using...

Using Python's pip to Manage Your Projects' Dependencies

In fact, the option to install pip with Python is checked by default, ... With the git+https scheme, you can point to a...