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.
pipenv shell creates new virtualenv
See original GitHub issueI forgot to cd to my project dir before running pipenv shell, and it created a new virtualenv.
Describe your environment
Windows 10 Python 3.6.4 Pipenv version: 11.1.5
Expected result
I would expect pipenv shell to fail when there is no virtualenv to start a shell for. I didn’t see anything in the docs about the shell command creating a virtualenv and Pipfile.
Actual result
A virtualenv was created and then a Pipfile and then pipenv crashed with a SyntaxError (but I see there’s already an issue for that).
Steps to replicate
Run pipenv shell in a directory with no Pipfile.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (3 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
this is intended behavior
I feel a PEEP proposing an environment variable disabling auto virtual environment creation in general (on just for
shell) could be appropriate.