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 steve.dower
Recipients cgohlke, jkloth, methane, ned.deily, paul.moore, steve.dower, tim.golden, zach.ware
Date 2017-10-07.15:43:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1507391032.98.0.213398074469.issue31340@psf.upfronthosting.co.za>
In-reply-to
Content
No, but if we need to do 3.6.4 quickly for another reason, let me know and I'll make this change.

It only affects people who are trying to share intermediate build files (which for MSVC purposes, includes static libraries) between their 3.6.2 and 3.6.3 builds. Full builds are going to be fine, and incremental builds should detect the changed tools and be able to rebuild everything. 

So it's solely cases where people are trying to manage the build around distutils rather than letting distutils handle it all that are problematic (and hey, both of these are terrible options! This is why we're discussing how to get people to just stop depending on distutils). I don't think it's worth churning the entire ecosystem just for that.
History
Date User Action Args
2017-10-07 15:43:53steve.dowersetrecipients: + steve.dower, paul.moore, tim.golden, jkloth, ned.deily, methane, cgohlke, zach.ware
2017-10-07 15:43:52steve.dowersetmessageid: <1507391032.98.0.213398074469.issue31340@psf.upfronthosting.co.za>
2017-10-07 15:43:52steve.dowerlinkissue31340 messages
2017-10-07 15:43:52steve.dowercreate