On Mon, Mar 27, 2006, Steven Bethard wrote: > > Abstract > ======== > > This PEP describes the procedure for changes to Python that introduce > backwards incompatible changes between the Python 2.X series and > Python 3000. All such changes must be documented by an appropriate > Python 3000 PEP and must be accompanied by code that can identify > when pieces of Python 2.X code will be incorrect in Python 3000.
s/incorrect/problematic/g There will be plenty of cases where code may be either correct or incorrect depending on the exact circumstances. Correctly determining whether any code is incorrect is impossible for a computer program; all we can guarantee is flagging code that *may* cause problems. -- Aahz ([EMAIL PROTECTED]) <*> http://www.pythoncraft.com/ "Look, it's your affair if you want to play with five people, but don't go calling it doubles." --John Cleese anticipates Usenet _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
