Fatal dependency resolution issue with editable dependencies
See original GitHub issueCheckout the code here and run test.sh
with the latest version of pipenv
to repro. Dependencies fail to resolve. If you revert to 2018.5.18
it works.
Additional info: moving the same sub-dependencies into the Pipfile
directly also allows pipenv
to resolve things properly (see the previous commit in the tree).
Issue Analytics
- State:
- Created 5 years ago
- Comments:22 (6 by maintainers)
Top Results From Across the Web
Dependency resolution failure with git packages from different ...
Run pip install -e . in that directory. Pip installs the package from the local source, it follows the dependencies to install https://github....
Read more >maven - Errors in pom.xml with dependencies (Missing artifact...)
It means maven is not able to download artifacts from repository. Following steps will help you: Go to repository browser and check if...
Read more >Dependency Scanning - GitLab Docs
The Dependency Scanning feature can automatically find security vulnerabilities in your software dependencies while you're developing and testing your ...
Read more >apt - How do I resolve unmet dependencies after adding a PPA?
One of the most basic fixes to resolve dependencies problems is to run: ... Packages are held because of dependency conflicts that apt...
Read more >IntelliJ IDEA - Troubleshooting common Maven issues
This error usually indicates a problem with the compiler version compatibility, and you can check few places to fix it. For example, you...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi - I downloaded and tried the latest release and this still seems to be a live issue. Can I help to move it forward in any way?
ssh://
totally works with GitHub. The problem is that we are using the wrong format; it should bessh://git@github.com/private/repo.git
instead.The problem likely lies into how requirementslib converts the URL before passing it into Git. We need to convert the
git@host:username/repo.git
format intossh://git@host/username/repo.git
so we can correctly parse it withurllib.parse
to get relevent URL information. I hope this helps you tracking down the problem