homepage

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 ezio.melotti
Recipients ezio.melotti, ocean-city, pitrou
Date 2009年02月13日.16:26:06
SpamBayes Score 1.9229306e-07
Marked as misclassified No
Message-id <1234542368.12.0.359022429385.issue5239@psf.upfronthosting.co.za>
In-reply-to
Content
Sorry, I misunderstood the meaning of "no-brainer".
If we add re.UNICODE on Py2, strptime should work fine with unicode
strings, but it could fail somehow with normal strings. Is it more
important to provide a way to use Unicode chars that works only with
unicode strings or to have a coherent behavior between str and unicode?
I don't think that adding re.UNICODE will break any existing code, but
it may cause problems if someone tries to use encoded str instead of
unicode (but shouldn't work already).
Also note that encoded strings should be a problem only if they have to
match a strptime directive (e.g. %Y), the other chars should be compared
as they are, so it should work with str and unicode as long as they are
not mixed (I think that whitespaces are treated differently though).
I'll try to add re.UNICODE and see what happens.
History
Date User Action Args
2009年02月13日 16:26:08ezio.melottisetrecipients: + ezio.melotti, pitrou, ocean-city
2009年02月13日 16:26:08ezio.melottisetmessageid: <1234542368.12.0.359022429385.issue5239@psf.upfronthosting.co.za>
2009年02月13日 16:26:07ezio.melottilinkissue5239 messages
2009年02月13日 16:26:06ezio.melotticreate

AltStyle によって変換されたページ (->オリジナル) /