You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before starting, ensure that you have done the following.
I have verified that there is no other issue or discussion covering the feature or enhancement
I have verified there is no open pull request for the feature or enhancement
I have verified the package to improve is located in this repository
What do you want to add?
There is no way to prevent Python installations from modifying the PATH variable unless you do a 32-bit only install. This is important for multiple Python installs, I don't want the installation of an older version to suddenly take precedent.
Currently, the way it works is through the use of the Install-Python helper function, which only takes into consideration whether the install is 32-bit or not. For normal installs, it will use PrependPath=1 as an argument for the installer.
What problem will the feature/enhancement solve?
When installing, say, the python310 package when I already have the python311 package, I won't have to worry about the python command suddenly pointing to the python310 installation.
If the feature or enhancement is approved:
I am willing to create a pull request to implement the feature or enhancement
Additional Context
While I'm willing to submit a PR myself to add this feature, I'm not sure how the new Python deployment process works, and I would like to be pointed to the exact file(s) to modify.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Before starting, ensure that you have done the following.
What do you want to add?
There is no way to prevent Python installations from modifying the PATH variable unless you do a 32-bit only install. This is important for multiple Python installs, I don't want the installation of an older version to suddenly take precedent.
Currently, the way it works is through the use of the Install-Python helper function, which only takes into consideration whether the install is 32-bit or not. For normal installs, it will use
PrependPath=1
as an argument for the installer.What problem will the feature/enhancement solve?
When installing, say, the python310 package when I already have the python311 package, I won't have to worry about the python command suddenly pointing to the python310 installation.
If the feature or enhancement is approved:
Additional Context
While I'm willing to submit a PR myself to add this feature, I'm not sure how the new Python deployment process works, and I would like to be pointed to the exact file(s) to modify.
Beta Was this translation helpful? Give feedback.
All reactions