This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ronaldoussoren
Recipients Arfrever, jkloth, ronaldoussoren
Date 2013-06-19.05:51:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1371621067.07.0.404545203428.issue18255@psf.upfronthosting.co.za>
In-reply-to
Content
I don't agree. Distutils still uses distutils.sysconfig for configuration information and setup.py wants to adjust that configuration, it should therefore use distutils.sysconfig instead of the global one. 

That said, it would be better to change distutils to use sysconfig instead of its local configuration information (distutils.sysconfig, distutils.command.install.INSTALL_SCHEMES, ...).  That has never been because distutils is frozen due to backward compatibility concerns, but it might be better to actually change distutils for 3.4 when there will be other changes to deal with the new packaging PEPs as well).

However: switching distutils to use the toplevel sysconfig will change functionality, as I wrote in my initial message you can use environment variables to override variables for distutils.sysconfig, but that doesn't work for the global sysconfig because the values in _sysconfigdata are expanded at build time.
History
Date User Action Args
2013-06-19 05:51:07ronaldoussorensetrecipients: + ronaldoussoren, jkloth, Arfrever
2013-06-19 05:51:07ronaldoussorensetmessageid: <1371621067.07.0.404545203428.issue18255@psf.upfronthosting.co.za>
2013-06-19 05:51:07ronaldoussorenlinkissue18255 messages
2013-06-19 05:51:06ronaldoussorencreate