[issue35667] activate for venv containing apostrophe doesn't work in powershell

Vinay Sajip added the comment: This has reportedly been fixed by the changes made to fix bpo-37354. I'll close this, but please reopen if you find it's still a problem. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___

[issue35667] activate for venv containing apostrophe doesn't work in powershell

Change by Derek Keeler : -- keywords: +patch pull_requests: +14736 stage: -> patch review pull_request: https://github.com/python/cpython/pull/14967 ___ Python tracker ___ ___

[issue35667] activate for venv containing apostrophe doesn't work in powershell

Eryk Sun added the comment: > I am not sure about the difference in semantics between powershell and > command prompt with respect to quoting since CMD only uses single quotes in `for /f` loops, in which it's either a command or a literal string (w/ the "usebackq" option). This is not a prob

[issue35667] activate for venv containing apostrophe doesn't work in powershell

Karthikeyan Singaravelan added the comment: >From the error I think the quotes are not properly escaped while doing text >replacement in venv activate file template at [0] while it's generated? On >linux/Mac double quotes are used and hence the error is not triggered with >single quote in vi

[issue35667] activate for venv containing apostrophe doesn't work in powershell

New submission from Cheryl Sabella : On Windows 10, when I try to activate a venv in powershell where the name contains an apostrophe, I get the following error ("don't" is the name of the venv): PS N:\projects\cpython\don't\Scripts> .\activate.ps1 At N:\projects\cpython\don't\Scripts\Activat