On 1 June 2015 at 00:44, Terry Reedy <tjreedy at udel.edu> wrote: > On 5/31/2015 6:59 AM, Alexander Walters wrote: >> >> A better course of action would be to deprecate the non-portable >> version. Other than setting the PATH envvar, why do we need to continue >> even touching the system on install? It is highly annoying for those of >> us that maintain several installs of python on a single windows system, >> and it really should stop. > > > Some people want the right-click context menu entries -- Run (also double > click) and Edit with Idle, which should be Edit with Idle x.y. And system administrators responsible for deploying and maintaining Standard Operating Environments want the MSI integration. In that regard, the default behaviour of the python.org installers is the rough equivalent of the system Python on Linux distributions (with the added complexity of needing to deal with the Windows registry). Portable installations are often good for developers, but they come at the cost of failing to integrate properly with the underlying operating system. Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4