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 lemburg
Recipients BreamoreBoy, christian.heimes, lemburg, paul.moore, steve.dower, tim.golden, zach.ware
Date 2015-05-11.17:48:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1431366492.37.0.569543886621.issue23970@psf.upfronthosting.co.za>
In-reply-to
Content
Why are you removing the mcvs9compiler.py file when at the same time your are referencing it in the msvccompiler.py doc string ?

--- a/Lib/distutils/msvccompiler.py
+++ b/Lib/distutils/msvccompiler.py
@@ -1,201 +1,120 @@
 """distutils.msvccompiler
 
 Contains MSVCCompiler, an implementation of the abstract CCompiler class
-for the Microsoft Visual Studio.
+for Microsoft Visual Studio 2015.
+
+The module is compatible with VS 2015 and later. You can find legacy support
+for older versions in distutils.msvc9compiler and distutils.msvccompiler.
 """

IMO, it would be better and more in line with the b/w aspects of distutils, to move the VS15 support into a new msvc14compiler.py
which is then imported by msvccompiler.py at the end (much like this was done for msvc9compiler.py.

That way we can maintain compatibility with existing code which uses stuff from those legacy modules.
History
Date User Action Args
2015-05-11 17:48:12lemburgsetrecipients: + lemburg, paul.moore, christian.heimes, tim.golden, BreamoreBoy, zach.ware, steve.dower
2015-05-11 17:48:12lemburgsetmessageid: <1431366492.37.0.569543886621.issue23970@psf.upfronthosting.co.za>
2015-05-11 17:48:12lemburglinkissue23970 messages
2015-05-11 17:48:12lemburgcreate