Robert Bradshaw, 27.07.2011 20:28:
Yes, that is a good point, though if it's (really) easy, I'd rather say "this is the last release supporting 2.3" rather than "oh, btw, we dropped support for 2.3."
I wouldn't mind either way. Let's see what the users poll gives.
I also think we should have a big fat #error rather than letting 2.3 support just fade away (or worse, silently produce bad/incorrect code).
With "fading out" I just meant that a) we don't even know right now if the C code we generate really works in Python 2.3 and b) we could just leave it that way and add a note to the release notes that it's no longer actively supported but on a "I feel lucky" basis.
But I agree that it's better to let the C compilation fail loudly, so that users know what the problem is.
Stefan _______________________________________________ cython-devel mailing list [email protected] http://mail.python.org/mailman/listinfo/cython-devel
