Pipenv no longer working under the root directory is not listed as a breaking change
See original GitHub issueIssue description
Our docker builds failed this morning due to a change in behaviour when running pipenv install
in the root directory.
When running with the latest version (2020.5.28) an error is thrown after dependencies are built and installed ERROR: Pipenv is not intended to work under the root directory, please choose another path.
It looks like this is a change introduced in #3386, relating to an issue raised in #3434.
This issue is really just to point out that this behaviour change should be listed as breaking in the changelog, as it doesn’t currently appear to be mentioned.
For the time being we have worked around this by pinning pipenv
to the last version (2018.11.26).
Expected result
N/A
Actual result
N/A
Steps to replicate
N/A
Issue Analytics
- State:
- Created 3 years ago
- Reactions:45
- Comments:28 (8 by maintainers)
Top Results From Across the Web
pipenv updates all dependencies bringing breaking changes
The problem is when I want to install a new depedency. I open the docker container shell, and I install the dependency with...
Read more >Common Pipenv Errors - Towards Data Science
The virtual environment is stored globally with the name of the project's root directory plus the hash of the full path to the...
Read more >pipenv Documentation - manpages.ubuntu!
To install packages, change into your project's directory (or just an empty directory for this tutorial) and run: $ cd myproject $ pipenv...
Read more >pipenv Documentation - Read the Docs
Running Pipenv as root or with sudo (or Admin on Windows) is highly discouraged and might lead to unintend breakage of your OS....
Read more >Pipenv & Virtual Environments
Python has included venv module from version 3.3. For more details: venv. Other Notes¶. Running virtualenv with the option --no-site ...
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 Free
Top 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
I can confirm that this behaviour does not happen on version
2018.11.26
.@mohamedMok You can use
pip install 'pipenv==2018.11.26'
which is the last version that does not have this breaking change.Using
WORKDIR
did not work for me. I’m getting errorwhen using dockerfile below