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 ncoghlan
Recipients Arfrever, DLitz, Natalia, barry, eric.araujo, ncoghlan, piotr, pitrou, samuel.lai, tarek
Date 2014-03-12.12:02:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Unfortunately, the current likely answer re updating vanilla distutils to handle the new standards is "we won't". The backwards compatibility issues involved are just too hairy for us to start enabling by default in the standard library, and I've become convinced that coupling the build and installation tools to the language version is fundamentally a mistake anyway (hence the bundling approach in PEP 453).

Instead, we're hacking around the metadata side of the problem through the fact that pip always runs under setuptools (even if the only used vanilla distutils) and encouraging the use of cross-version compatible tools in other cases (with setuptools being the current de facto choice, since the distlib APIs are still considered experimental).

For this particularly case, I don't see any harm in bringing distutils in Py3 back in line with Py2, especially if it's also consistent with setuptools.
Date User Action Args
2014-03-12 12:02:26ncoghlansetrecipients: + ncoghlan, barry, pitrou, tarek, eric.araujo, Arfrever, piotr, Natalia, DLitz, samuel.lai
2014-03-12 12:02:26ncoghlansetmessageid: <>
2014-03-12 12:02:26ncoghlanlinkissue14894 messages
2014-03-12 12:02:25ncoghlancreate