Marc-Andre Lemburg added the comment: On 17.04.2015 16:04, Steve Dower wrote: > > Yeah, the basic functionality is no different, since there isn't really a > better way to handle future versions of VS automatically. I'd rather not > officially expose this stuff though. > > Maybe you could override the compiler creation code and return an alternative > implementation? That will be most portable.
I just had a look at our code and I think we can try a different approach which doesn't require monkey-patching: we're using a CompilerSupportMixin for the build commands which has a .prepare_compiler() method to set up the .compiler attribute which is then used for compiling things. We'll have to experiment with that a bit, since I'm not sure whether this will catch all cases where distutils uses a compiler. Alternatively, we could use monkey-patching (again :-() to override ccompiler.new_compiler() and then apply the fixes there. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue23970> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
