On 3/4/06, Anthony Baxter <[EMAIL PROTECTED]> wrote: > On Saturday 04 March 2006 15:34, Tim Peters wrote: > > Indeed! But whose arm could we twist to get them to repair the > > compiler in 2.4? I'd settle for a blurb in the next 2.4 NEWS just > > noting that 2.5 will follow the documented syntax. That may even > > be desirable, to avoid breaking working (albeit by accident) code > > across a micro release. > > 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. 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. -- --Guido van Rossum (home page: http://www.python.org/~guido/) _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
