Steven D'Aprano wrote:
On Mon, 10 Aug 2009 08:21:03 -0700, Douglas Alan wrote:
But you're right, it's too late to change this now.
Not really. There is a procedure for making non-backwards compatible
changes. If you care deeply enough about this, you could agitate for
Python 3.2 to raise a PendingDepreciation warning for "unexpected" escape
sequences like \z, Python 3.3 to raise a Depreciation warning, and Python
3.4 to treat it as an error.
It may even be possible to skip the PendingDepreciation warning and go
straight for Depreciation warning in 3.2.
And once it's fully depreciated you have to stop writing it off on your
taxes. *wink*
~Ethan~
--
http://mail.python.org/mailman/listinfo/python-list
