RetroSearch Browse

Tue Mar 1 08:24:08 EST 2016 · https://mail.python.org/pipermail/python-dev/2016-March/143444.html

On 1 March 2016 at 11:37, David Cournapeau <cournape at gmail.com> wrote:
> I am not clear about 3., especially on what should be changed. I know that
> for 2.7, we need to change PC\getpathp.c for sys.path, but are there any
> other places where the registry is used by python itself ?

My understanding from the earlier discussion was that you should not
patch Python at all. The sys.path building via PythonPath is not
covered by the PEP and you should continue as at present. The new keys
are all for informational purposes - your installer should write to
them, and read them if looking for your installations. But the Python
interpreter itself should not know or care about your new keys.

Steve can probably clarify better than I can, but that's how I recall
it being intended to work.
Paul

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2016-March/143444.html below:

[Python-Dev] PEP 514: Python environment registration in the Windows Registry