"Josiah Carlson" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Personally, I see Py3k as a vetting mechanism for all those hair-brained > ideas that really shouldn't make it into any Python version (3k or > otherwise), with the possible inclusion of things that *should* make > life better for Python users. With that said, aside from the stdlib > reorganization (which should happen in the 2.x series anyways), so far I > haven't seen anything that necessitates backwards incompatible changes > to Python 3k, and I predict that many of the changes to py3k will be > included into mainline 2.x during 3k's development.
The somewhat backwards-incompatible integer division change discussed and approved some years ago has been suspended pending 3.0, so since I would like to not have to (indefinitely) import 'division' from __future__ to get the change, I too, on that score, would like to see 3.0 sooner than later. Terry Jan Reedy _______________________________________________ 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
