Message81934
| Author |
pitrou |
| Recipients |
ezio.melotti, ocean-city, pitrou |
| Date |
2009年02月13日.14:24:36 |
| SpamBayes Score |
1.7124448e-05 |
| Marked as misclassified |
No |
| Message-id |
<1234535121.7339.9.camel@fsol> |
| In-reply-to |
<1234534387.8.0.987702618269.issue5239@psf.upfronthosting.co.za> |
| Content |
> Hmm, this fails on python2 too. Maybe re.ASCII is added for backward
> compatibility? Again, I'm not familiar with unicode, so I won't call
> remove_ascii_flag.patch as *fix*.
re.ASCII was added to many stdlib modules because I wanted to minimize
the potential for breakage when I converted the re library to use
unicode matching by default.
If it is desireable for strptime() and friends to match unicode digits
as well as pure-ASCII digits (which sounds like a reasonable request to
me), then re.ASCII can probably be dropped without any regret.
(py3k doesn't have to be 100% compatible with python2 :-)) |
|