On Sat, Jan 15, 2011 at 1:02 PM, Stefan Behnel <stefan...@behnel.de> wrote: > Robert Bradshaw, 15.01.2011 21:26: >> Whether it's the -2 flag, or something else, we should at least have a >> mode that handles things exactly as they would be handled in Python 2. >> Otherwise people won't be able to just compile their existing code >> without worrying about subtle issues like this. > > Hmm. I wouldn't mind having a mode that compiles Python 2 code and fails > fast on compilation under Python 3 with a C "#error" - if someone has > enough interest in this to implement it. I certainly don't.
That's an interesting idea. > While I agree > that these issues are subtle, they certainly aren't common enough to really > worry about them. Broken code is best worked around by fixing the code. > Even the Python 2.x line hasn't always bowed to the holy cow of backwards > compatibility. > > Anyway, given that "-3" doesn't prevent code from working in Python 2, the > "-2" flag doesn't seem like a good match. It should be something clear as > in "--python2-only". I think the primary motivation of the -2 flag is so that, eventually, we can make -3 the default without providing a recourse for people who don't want to change their code right away. - Robert _______________________________________________ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
