classification
Title: Script name for venv PowerShell activate
Type: enhancement Stage:
Components: Library (Lib) Versions:
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: paul.moore, pwatson, steve.dower, tim.golden, vinay.sajip, zach.ware
Priority: normal Keywords:

Created on 2021-07-13 15:04 by pwatson, last changed 2021-07-19 13:38 by vinay.sajip.

Messages (2)
msg397416 - (view) Author: Paul Watson (pwatson) Date: 2021-07-13 15:04
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.
msg397796 - (view) Author: Vinay Sajip (vinay.sajip) * (Python committer) Date: 2021-07-19 13:38
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 the wild follow these namig conventions rigidly - that hasn't been my experience. Is it the case? Who polices that? Of course, in environments that mandate this level of conformance, you can easily subclass and override the relevant functionality to have the script be named exactly how you want.
History
Date User Action Args
2021-07-19 13:38:03vinay.sajipsetmessages: + msg397796
2021-07-16 18:51:57eric.araujosetnosy: + vinay.sajip
components: + Library (Lib), - Installation
2021-07-13 16:14:34ammar2setnosy: + paul.moore, tim.golden, zach.ware, steve.dower
2021-07-13 15:04:11pwatsoncreate