[issue44624] Script name for venv PowerShell activate

Vinay Sajip added the comment: In this case, there are two reasons IMO for not doing this: 1. Backward compatibility might be affected. 2. It may be more important to conform to venv conventions than Powershell conventions in this specific case. I wasn't aware that PowerShell scripts out in

[issue44624] Script name for venv PowerShell activate

Change by Éric Araujo : -- components: +Library (Lib) -Installation nosy: +vinay.sajip ___ Python tracker ___ ___ Python-bugs-list ma

[issue44624] Script name for venv PowerShell activate

Change by Ammar Askar : -- nosy: +paul.moore, steve.dower, tim.golden, zach.ware ___ Python tracker ___ ___ Python-bugs-list mailing

[issue44624] Script name for venv PowerShell activate

New submission from Paul Watson : In the venv .\Scripts directory. the name 'Activate.ps1' does not conform to the PowerShell prescribed Verb-Noun format. How about using 'Initialize-Python.ps1' as the script name? Or, something else that does conform to PowerShell standard naming. -