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.
Installing private repo with git+git is not working at 2018.7.1 version
See original GitHub issueThis works with older version: pipenv version: 11.10.1 pipenv install -e git+git@github.com:some/repo.git#egg=foo\&subdirectory=sub
Running same command with version: 2018.7.1. First part succeeds, then second part fails.
Installing ...
Obtaining foo from git+git@github.com:CloudVLab/fusion.git#egg=Fusion&subdirectory=python
...
Successfully installed foo
Adding -e git+git@github.com:... to Pipfile's [packages]...
Pipfile.lock (a34c46) out of date, updating to (0c0917)...
Locking [dev-packages] dependencies...
Locking [packages] dependencies...
...
Command "git clone -q ssh://git@github.com:some/repo.git /tmp/tmptsmueli7source/foo" failed with error code 128 in None
...
Pipenv should either do(both commands are exactly same AFAIK):
git clone git@github.com:some/repo.git
or
git clone ssh://git@github.com/some/repo.git
notice the : vs /
instead it is doing:
ssh://git@github.com:some/repo.git
which obviously not working.
As a workaround I had to do:
pipenv install -e git+ssh://git@github.com/some/repo.git
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Nope, I tried it. Works. Thank you!
This is resolved in what will be the next release (I’d link to the issues but we fixed it some time ago)
Have been slammed on our end lately, but should be able to get the release out shortly – sorry for the issue!