pipenv shell --fancy doesn't see any of the packages installed
See original GitHub issueIf I run pipenv shell --fancy
then when I run my script it complains that none of the packages installed with pipenv install
are available.
IfI run just pipenv shell
it works and packages are recognized and script works but it messes up the shell (oh-my-zsh/prezto/fish).
pipenv, version 2018.10.13
Python 3.7.2
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Frequently Encountered Pipenv Problems - Read the Docs
This is usually a result of mixing Pipenv with system packages. We strongly recommend installing Pipenv in an isolated environment. Uninstall all existing ......
Read more >How can I see the current version of packages installed by ...
1.go in project folder. 2.first activate pipenv type pipenv shell . 3.type pip freeze.
Read more >pipenv Documentation - Read the Docs
Pipenv is a tool that aims to bring the best of all packaging worlds (bundler, composer, npm, cargo, yarn, etc.) to the. Python...
Read more >Advanced Usage of Pipenv - Python Packaging Authority
Pipenv allows you to open any Python module that is installed (including ones in your codebase), with the $ pipenv open command: $...
Read more >Advanced Usage of Pipenv — pipenv 7.7.9 documentation
$ pipenv install¶ · --dev — Install both develop and default packages from Pipfile.lock . · --system — Use the system pip command...
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’m running into the same issue. It seems like the answer to our issue is discussed here however, I haven’t been able to fix it.
The way I’m interpreting those instructions, is that I need to go into my shell config file and wrap everything in an
if status --is-login
block. Tried that but it doesn’t resolve the issue but can confirm that nothing in theif
block runs when usingpipenv shell --fancy
.The only difference between using fancy and not using it is the
source ...
line appears in the latter. Other than that, I’m stuck. Sorry, wish I could be more helpful.PS: Beware, changes you make when
--fancy
fails to enter your virtual environment can affect your system-wide packages. I learned that the hard way.Hey @techalchemy, no need to reopen the issue or anything but I ran
--support
and just thought I’d post it here in case you see anything obvious. My workaround at the moment is not to use the--fancy
option and to avoid having the repo name show up twice, I settheme_display_virtualenv
to no, so that’s been working well enough for me so far 😃