Marc-Andre Lemburg <m...@egenix.com> added the comment: Tarek Ziadé wrote: > Tarek Ziadé <ziade.ta...@gmail.com> added the comment: > > I'll set back the compiler attribute when compiler_obj is set too, > so third-party code will be able to work with it as before. > > The current code will deprecate this usage, by displaying a deprecation > warning: > > - if the compiler is set to anything else than a string. > - if the compiler is get and happens to be a compiler instance. > > so we can keep "compiler" as its initial purpose.
Could you please elaborate a bit on the reasoning behind deprecating using .compiler for the compiler instance ? The code did work before, so I'm not sure why you are trying to fix something that wasn't really broken. With the change you: * make the code more complex just to be able to raise a warning * introduce an cross-version incompatibility for tools using build_ext: they will now have to use .compiler for Python 2.3-2.6 and .compiler_obj for 2.7 and up Wouldn't it be better to either leave things are they have been for years (without problems) or find another solution ? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue6377> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
