I haven't read that thread yet (and probably never will), but I want to draw a line in the sand. In order to avoid a slippery slope, I'm not putting backwards compatibility in 3.0 for stuff we want killed *except* for certain exceptions that 2to3 can't fix. (The only one I am aware of being % formatting, which will survive alongside .format() for now.)
Hopefully this will kill the discussion. --Guido On Mon, Mar 24, 2008 at 11:05 AM, Charles Merriam <[EMAIL PROTECTED]> wrote: > OK. 54 long messages into it, the argument is stuck at: > > 1. But 3.0 code is different. > 2. But 3.0 shouldn't gratuitously break 2.6 code. > > So make u"sting" a deprecated structure with a warning and kill it in > 3.1. Why write a novel about it? Just make what programmers expect > to happen happen. > > > Charles > _______________________________________________ > Python-3000 mailing list > [email protected] > http://mail.python.org/mailman/listinfo/python-3000 > Unsubscribe: > http://mail.python.org/mailman/options/python-3000/guido%40python.org > -- --Guido van Rossum (home page: http://www.python.org/~guido/) _______________________________________________ Python-3000 mailing list [email protected] http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
