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 BreamoreBoy, christian.heimes, lemburg, paul.moore, steve.dower, tim.golden, zach.ware
Date 2015-05-19.17:13:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1432055602.4.0.780529706026.issue23970@psf.upfronthosting.co.za>
In-reply-to
Content
New patch. I've renamed the new class _msvccompiler and changed ccompiler to use it instead of the old ones.

The old ones are still there to avoid breaking people who were using them directly, and the old tests are still there too.

Personally, I expect subtle breakages in actual use (that we couldn't possible test for reliably) and I don't like deliberately leaving cruft behind, but it seems like the best way to move forward without breaking people.

Would adding a deprecation warning to the orphaned modules make sense? They should never be imported in normal use.
History
Date User Action Args
2015-05-19 17:13:26steve.dowersetrecipients: + steve.dower, lemburg, paul.moore, christian.heimes, tim.golden, BreamoreBoy, zach.ware
2015-05-19 17:13:22steve.dowersetmessageid: <1432055602.4.0.780529706026.issue23970@psf.upfronthosting.co.za>
2015-05-19 17:13:22steve.dowerlinkissue23970 messages
2015-05-19 17:13:19steve.dowercreate