PowerShell prompt string not modified by poetry shell

[AndreaCogliati]

• 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 Home 21H1 (OS Build 19043.1237)
• Poetry version: 1.1.10
• Link of a Gist with the contents of your pyproject.toml file: https://gist.github.com/AndreaCogliati/9cf936e10b14f73506bb3b79569a51f7

Issue

poetry shell doesn't update the PowerShell prompt string, so there's no visual cue that a poetry environment is active in the current shell. See sample output:

Poetry (1.1.10) is installed now. Great!
PS C:\Users\Andrea Cogliati\source\repos\pigs> poetry new poetry-demo
Created package poetry_demo in poetry-demo
PS C:\Users\Andrea Cogliati\source\repos\pigs> cd .\poetry-demo\
PS C:\Users\Andrea Cogliati\source\repos\pigs\poetry-demo> poetry shell
Creating virtualenv poetry-demo-g8BhE-uU-py3.7 in C:\Users\Andrea Cogliati\AppData\Local\pypoetry\Cache\virtualenvs
Spawning shell within C:\Users\Andrea Cogliati\AppData\Local\pypoetry\Cache\virtualenvs\poetry-demo-g8BhE-uU-py3.7
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Try the new cross-platform PowerShell https://aka.ms/pscore6

PS C:\Users\Andrea Cogliati\source\repos\pigs\poetry-demo> ls


    Directory: C:\Users\Andrea Cogliati\source\repos\pigs\poetry-demo


Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
d-----         9/25/2021   4:31 PM                poetry_demo
d-----         9/25/2021   4:31 PM                tests
-a----         9/25/2021   4:31 PM            324 pyproject.toml
-a----         9/25/2021   4:31 PM              0 README.rst

PS C:\Users\Andrea Cogliati\source\repos\pigs\poetry-demo> $host.version

Major  Minor  Build  Revision
-----  -----  -----  --------
5      1      19041  1237

[github-actions]

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.