[Python-Dev] Bug in from future processing? (original) (raw)

Fredrik Lundh fredrik at pythonware.com
Mon Mar 6 07:17:00 CET 2006

Guido van Rossum wrote:

> I don't think a change like this should go into a 2.4.x release. It > stands a very very high chance of breaking someone's code. I could > be convinced about a warning being emitted about it, though I'm not > going to have the time to figure out the new compiler to do the work.

In fact I know for sure it will break code -- I believe I first ran into this with Django.

Cheetah ?

http://www.artima.com/weblogs/viewpost.jsp?thread=146606

Let's leave 2.4 alone (even adding a warning to 2.4.3 seems pointless) except for documenting this (not just in Misc/NEWS which is overwhelming but in the 2.4 docs for future-). In 2.5 it's already fixed; perhaps the 2.5 docs could mention that this was accidentally broken in 2.4.

agreed.

More information about the Python-Dev mailing list