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.

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

Poetry does not show the virtualenv prefix on PowerShell #5824

Closed
3 tasks done
Lazza opened this issue Jun 10, 2022 · 2 comments
Closed
3 tasks done

Poetry does not show the virtualenv prefix on PowerShell #5824

Lazza opened this issue Jun 10, 2022 · 2 comments
Labels
area/windows For Windows-specific issues kind/bug Something isn't working as expected

Comments

@Lazza
Copy link

Lazza commented Jun 10, 2022

  • 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 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:

C:\Users\andrea\AppData\Local\pypoetry\Cache\virtualenvs\REDACTED-WpnDpl_K-py3.9\Scripts\activate

However, the virtual environment name is shown when manually running the PowerShell activation script:

C:\Users\andrea\AppData\Local\pypoetry\Cache\virtualenvs\REDACTED-WpnDpl_K-py3.9\Scripts\activate.ps1

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.

@Lazza Lazza added kind/bug Something isn't working as expected status/triage This issue needs to be triaged labels Jun 10, 2022
@Secrus Secrus added the area/windows For Windows-specific issues label Jun 13, 2022
@bmarroquin
Copy link
Contributor

closed by #5053. already available in 1.2 beta

@mkniewallner mkniewallner removed the status/triage This issue needs to be triaged label Sep 18, 2022
Copy link

github-actions bot commented Mar 1, 2024

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 1, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/windows For Windows-specific issues kind/bug Something isn't working as expected
Projects
None yet
Development

No branches or pull requests

5 participants