You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the issues of this repo and believe that this is not a duplicate.
If an exception occurs when executing a command, I executed it again in debug mode (-vvv option).
OS version and name: Windows 10
Poetry version: 1.1.13 installed via Pip
Link of a Gist with the contents of your pyproject.toml file: N/A
Issue
When running poetry shell, it looks like Poetry runs the virtualenv activation. However, it does not show the visual cue in the command prompt, e.g.:
D:\repo\REDACTED [master ≡]> poetry shell
Spawning shell within C:\Users\andrea\AppData\Local\pypoetry\Cache\virtualenvs\REDACTED-WpnDpl_K-py3.9
Windows PowerShell
Copyright (C) Microsoft Corporation. Tutti i diritti riservati.
Prova la nuova PowerShell multipiattaforma https://aka.ms/pscore6
D:\repo\REDACTED [master ≡]>
The same happens if I intentionally run the "wrong" activation script (the cmd one) manually:
Sadly, the virtualenv name is added at the end, and not at the beginning of the prompt, like the standard venv module (not virtualenv) does. But that's just a personal preference.
The text was updated successfully, but these errors were encountered:
I am on the latest Poetry version.
I have searched the issues of this repo and believe that this is not a duplicate.
If an exception occurs when executing a command, I executed it again in debug mode (
-vvv
option).OS version and name: Windows 10
Poetry version: 1.1.13 installed via Pip
Link of a Gist with the contents of your pyproject.toml file: N/A
Issue
When running
poetry shell
, it looks like Poetry runs thevirtualenv
activation. However, it does not show the visual cue in the command prompt, e.g.:The same happens if I intentionally run the "wrong" activation script (the
cmd
one) manually:However, the virtual environment name is shown when manually running the PowerShell activation script:
Sadly, the virtualenv name is added at the end, and not at the beginning of the prompt, like the standard
venv
module (notvirtualenv
) does. But that's just a personal preference.The text was updated successfully, but these errors were encountered: