Stuck on an issue?

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.

terminal prompt doesn't show you're in the venv

See original GitHub issue

I’m on OS X Sierra running pipenv 3.5.2. Everything seems to work correctly. But when dropping into shell:pipenv shell I get Launching subshell in virtual environment... However the terminal prompt doesn’t change to show I’m in the virtual environment - looks like my normal terminal prompt. Examples I see in the doc, look like the prompt should change as it does in virtualenvironment. Is there a configuration setting I’m missing? Thanks

Issue Analytics

State:
Created 7 years ago
Comments:7 (4 by maintainers)

Top GitHub Comments

3reactions

nateprewittcommented, Mar 13, 2017

If that doesn’t work, pipenv shell -c should fix your issue. This appears to be a dupe of a conflict we’ve previously found with pew.

0reactions

davebrysoncommented, Mar 13, 2017

Thanks for the quick response and great work on pipenv!

Top Results From Across the Web

bash - Why is virtualenv not setting my terminal prompt?

My mistake - it looks like I have a git-aware prompt which is overwriting the prompt depending on the directory / repo status....

PowerShell prompt doesn't show virtualenv : PY-22469

There's a workaround for this issue. Under Settings > Tools > Terminal you can uncheck the Activate virtualenv option and then set the...

Can't see python virtual environment name in bash prompt ...

When it is active, I mean after exec bash , if I create a virtual environment with virtualenv venv and subsequently activate it...

How To Set Up a Virtual Python Environment (Windows)

Now that we have a virtual environment, we need to activate it. .\venv\Scripts\activate. After you activate the environment, your command prompt will be ......

How to customize the bash prompt in a way that doesn't ...

As a (bad) workaround, you can define bash functions that set and unset prefix for PS1 , and call these when you activate/deactivate...