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.
Absolute paths for -e . in lock -r
See original GitHub issueSince 2018.6.25, pipenv install --dev -e . gets resolved to absolute paths when running pipenv lock --requirements --dev >dev-requirements.txt.
That has the downside, that that .txt is only usable by the person who locked the dependencies if you (like us and I’m sure many more) use Pipenv to manage your deps, but use standard .txt files to deploy/tox.
I’m sure you had good reasons to change this behavior but it would be great to have an option to get the old back.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:7 (4 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
Thank you for the input. We are already investigating the issue, and will definitely fix this as soon as possible. Please do provide help if this is an urgent issue for you.
👎 Absolute paths are not portable 😦 It is very bad changes. We use
pipenv install -e .This behavior killing usage pipenv in our team project. We are saddened by this change.