Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add details to basic usage docs about setting VIRTUAL_ENV_DISABLE_PROMPT #7874

Merged
merged 3 commits into from
May 8, 2023
Merged

Add details to basic usage docs about setting VIRTUAL_ENV_DISABLE_PROMPT #7874

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ab7bf99
Formatting
May 4, 2023
8e396f4
Move to activating virtual env section
May 8, 2023
f19155d
Move up before manual env activation
May 8, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions docs/basic-usage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -149,6 +149,9 @@ Therefore, Poetry has to create a sub-shell with the virtual environment activat
in order for the subsequent commands to run from within the virtual environment.
{{% /note %}}

If you'd like to prevent `poetry shell` from modifying your shell prompt on virtual environment activation, you should
set `VIRTUAL_ENV_DISABLE_PROMPT=1` as an environment variable before running the command.

Alternatively, to avoid creating a new shell, you can manually activate the
virtual environment by running `source {path_to_venv}/bin/activate` (`{path_to_venv}\Scripts\activate.ps1` in PowerShell).
To get the path to your virtual environment run `poetry env info --path`.
Expand Down