[Python-Dev] PEP 514: Python environment registration in the Windows Registry
Steve Dower
steve.dower at python.org
Tue Mar 1 15:25:57 EST 2016
More information about the Python-Dev mailing list
Tue Mar 1 15:25:57 EST 2016
- Previous message (by thread): [Python-Dev] PEP 514: Python environment registration in the Windows Registry
- Next message (by thread): [Python-Dev] Question about sys.path and sys.argv and how packaging (may) affects default values
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 01Mar2016 1137, David Cournapeau wrote: > If you want to patch your own distribution to move the paths you are > welcome to do that - there is only one string literal in getpathp.c > that needs to be updated - but it's not a requirement and I > deliberately avoided making a recommendation either way. (Though as > discussed earlier in the thread, I'm very much in favour of > deprecating and removing any use of the registry by the runtime > itself in 3.6+, but still working out the implications of that.) > > > Great, I just wanted to make sure removing it ourselves do not put us in > a corner or further away from where python itself is going. > > Would it make sense to indicate in the PEP that doing so is allowed > (neither recommended or frowned upon) ? I was hoping not, but I suspect the question will come up again, so best to address it once in the official doc. Cheers, Steve
- Previous message (by thread): [Python-Dev] PEP 514: Python environment registration in the Windows Registry
- Next message (by thread): [Python-Dev] Question about sys.path and sys.argv and how packaging (may) affects default values
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list