Author steve.dower
Recipients TBBle, docs@python, eryksun, paul.moore, steve.dower, tim.golden, zach.ware
Date 2017-03-19.18:41:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1489948869.52.0.769949968735.issue29844@psf.upfronthosting.co.za>
In-reply-to
Content
Maybe I need to look through the history to see whether I actually intended the all-users install to be in System, but I don't think I did (despite writing the documentation linked - it may have been adapted from the old documentation).

Applications that need Python should look in the registry or embed the embeddable distro, depending on whether they are providing access to the user's own Python (e.g. an IDE) or it's an internal implementation detail (e.g. a tool that just happens to be implemented using Python). The former should really offer options for the user to specify a path to the install as well.

Reliably finding the required standard library for a copy of Python that is installed somewhere else is every bit as problematic as locating the install itself. When everyone follows PEP 514 properly it may be safe for a System32-DLL to use the registry again for finding its library, but as long as various distros want to overwrite the core registry keys, everyone is better off without it being a system component.
History
Date User Action Args
2017-03-19 18:41:09steve.dowersetrecipients: + steve.dower, paul.moore, tim.golden, TBBle, docs@python, zach.ware, eryksun
2017-03-19 18:41:09steve.dowersetmessageid: <1489948869.52.0.769949968735.issue29844@psf.upfronthosting.co.za>
2017-03-19 18:41:09steve.dowerlinkissue29844 messages
2017-03-19 18:41:09steve.dowercreate