Failed parsing requirement error for local dependency
See original GitHub issueRelease https://github.com/pypa/pipenv/releases/tag/v2022.8.24 introduces a bug about resolving local dependencies with a relative path.
Our setup has a local dependency described as {path = "./shared", extras = ["models", "auth0"]}
in Pipfile.
pipenv install
throws error: pipenv.vendor.requirementslib.exceptions.RequirementError: Failed parsing requirement from './shared#egg='
reverting to the previous release https://github.com/pypa/pipenv/releases/tag/v2022.8.19 fixes the issue for us.
Issue Analytics
- State:
- Created a year ago
- Comments:10
Top Results From Across the Web
How to fix locking failed in pipenv? - Stack Overflow
The error you get when you first run pipenv install with pipenv version 2020.8.13 . ... Requirement.parse('importlib-metadata<2,>=0.12; ...
Read more >Dependency Scanning - GitLab Docs
If a non-fatal error is encountered, the analyzer falls back to parsing the available go.sum file. The process is repeated for every detected...
Read more >pip install - pip documentation v22.3.1
python -m pip install [options] <requirement specifier> ... Local directory (which must contain a setup.py , or pip will report an error).
Read more >Errors while running pip install -r requirements.txt - MongoDB
I am getting these kinds of error while running pip install -r ... errored out with exit status 1: command: 'c:\users\manan\appdata\local…
Read more >Learning the Basics - Gradle User Manual
Before adding Maven local as a repository, you should make sure this is really required. To declare the local Maven cache as a...
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
I have already fixed the version to 2022.8.30 in all dockerfiles where we install pipenv. By the looks, #5320 seems to fix it. But it will be much easier for me to validate by the next release.
@mstdokumaci I see what you mean about this example, it may be a new requirementslib issue–however, if you add
editable = "true",
to your local dependency it appears to work. Here was the stack trace I got without havingeditable = "true",