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, benjamin.peterson, christian.heimes, lemburg, paul.moore, python-dev, steve.dower, tim.golden, zach.ware
Date 2015-05-27.09:53:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1432720410.05.0.105336227318.issue23970@psf.upfronthosting.co.za>
In-reply-to
Content
I was away the last few days, so just found the changes now.

IMO, it's a good idea to use a new module for the new compiler, but don't think it's a good idea to make the whole module private, since this implicitly disallows sub-classing the compiler class going forward, which people will need to do sooner or later.

Why not rename the module to msvc14compiler (or some other public name) instead ?
History
Date User Action Args
2015-05-27 09:53:30lemburgsetrecipients: + lemburg, paul.moore, christian.heimes, tim.golden, benjamin.peterson, BreamoreBoy, python-dev, zach.ware, steve.dower
2015-05-27 09:53:30lemburgsetmessageid: <1432720410.05.0.105336227318.issue23970@psf.upfronthosting.co.za>
2015-05-27 09:53:30lemburglinkissue23970 messages
2015-05-27 09:53:30lemburgcreate