Author ned.deily
Recipients jaraco, ncoghlan, ned.deily, tarek
Date 2013-07-08.19:05:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
There have been a number of issues that have come up over the past few years due to Python 3.2+'s distutils being a subset of Python 2.7's as a result of the revert (29a3eda89995).  Since circumstances have changed since the decision was made to do the revert and distutils isn't going away immediately, I think the best thing at this point would be for someone to make a comprehensive forward port patch of the current distutils in 2.7 to default for review with the goal of having a common base, feature- and bug-wise, for 3.4.  That isn't going to solve the problem for those who need to support 3.2, of course, but knowing exactly what the differences are at this point might suggest some practical solutions, as I expect the differences among 3.2, 3.3, and default (3.4) at this point are fewer than the differences between any of them and 2.7.  A first step would be to open an issue.
Date User Action Args
2013-07-08 19:05:59ned.deilysetrecipients: + ned.deily, jaraco, ncoghlan, tarek
2013-07-08 19:05:59ned.deilysetmessageid: <>
2013-07-08 19:05:59ned.deilylinkissue7457 messages
2013-07-08 19:05:58ned.deilycreate