Message90309
Tarek Ziadé wrote:
> Tarek Ziadé <ziade.tarek@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 ? |
|
Date |
User |
Action |
Args |
2009-07-09 07:55:15 | lemburg | set | recipients:
+ lemburg, exarkun, atuining, benjamin.peterson, tarek, rpetrov |
2009-07-09 07:55:14 | lemburg | link | issue6377 messages |
2009-07-09 07:55:13 | lemburg | create | |
|