➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients ezio.melotti, ocean-city, pitrou
Date 2009-02-13.14:50:33
SpamBayes Score 7.185071e-07
Marked as misclassified No
Message-id <1234536677.7339.12.camel@fsol>
In-reply-to <1234536262.25.0.0826031247434.issue5239@psf.upfronthosting.co.za>
Content 
Le vendredi 13 février 2009 à 14:44 +0000, Ezio Melotti a écrit :
> It's probably a good idea to have a coherent behavior between Py2 and
> Py3, so if we remove re.ASCII from Py3 we should add re.UNICODE to Py2.

Removing re.ASCII in py3k is a no-brainer, because unicode is how
strings work by default.
On the other hand, strings in 2.x are 8-bit, so it would probably be
better to keep strptime as is.
As I said, py3k doesn't have to be compatible with 2.x, that's even the
whole point of it.
History
Date User Action Args
2009-02-13 14:50:35pitrousetrecipients: + pitrou, ocean-city, ezio.melotti
2009-02-13 14:50:33pitroulinkissue5239 messages
2009-02-13 14:50:33pitroucreate