[issue2834] re.IGNORECASE not Unicode-ready

Changes by Ezio Melotti : -- nosy: +ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue2834] re.IGNORECASE not Unicode-ready

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Thanks a lot Mark! ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list mailing

[issue2834] re.IGNORECASE not Unicode-ready

Mark Summerfield <[EMAIL PROTECTED]> added the comment: On 2008-08-19, Antoine Pitrou wrote: > Antoine Pitrou <[EMAIL PROTECTED]> added the comment: > > Fixed in r65860. Someone should check the docs though (at least try to > generate them, and review my changes a bit since English isn't my mothe

[issue2834] re.IGNORECASE not Unicode-ready

Mark Summerfield <[EMAIL PROTECTED]> added the comment: On 2008-08-19, Antoine Pitrou wrote: > Antoine Pitrou <[EMAIL PROTECTED]> added the comment: > > Fixed in r65860. Someone should check the docs though (at least try to > generate them, and review my changes a bit since English isn't my mothe

[issue2834] re.IGNORECASE not Unicode-ready

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Fixed in r65860. Someone should check the docs though (at least try to generate them, and review my changes a bit since English isn't my mother tongue). -- resolution: accepted -> fixed status: open -> closed

[issue2834] re.IGNORECASE not Unicode-ready

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: Make sure of course that the documentation is updated and a NEWS file entry is added. ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue2834] re.IGNORECASE not Unicode-ready

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: I haven't looked at the specific patch, but based on the description of the behavior, I'm +1 on committing this before beta 3. I'm fine with leaving the re.ASCII flags in there -- it will be a marker to indicate perhaps the code needs a clos

[issue2834] re.IGNORECASE not Unicode-ready

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Barry? ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list mailing list Unsubsc

[issue2834] re.IGNORECASE not Unicode-ready

Guido van Rossum <[EMAIL PROTECTED]> added the comment: Let's make sure the release manager is OK with this. -- nosy: +barry ___ Python tracker <[EMAIL PROTECTED]> ___

[issue2834] re.IGNORECASE not Unicode-ready

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: If nobody (except Amaury :-)) has anything to say about the current patch, should it be committed? ___ Python tracker <[EMAIL PROTECTED]> _

[issue2834] re.IGNORECASE not Unicode-ready

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Le lundi 28 juillet 2008 à 20:41 +, Amaury Forgeot d'Arc a écrit : > Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: > > Are all those re.ASCII flags mandatory, or are they here just for > theoretical correctness? For theoret

[issue2834] re.IGNORECASE not Unicode-ready

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: Are all those re.ASCII flags mandatory, or are they here just for theoretical correctness? For example, the output of "gcc -dumpversion" is certainly plain ASCII. I don't mind that \d also matches some exotic digit - it just won't happen

[issue2834] re.IGNORECASE not Unicode-ready

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Final patch adding the (?a) inline flag (equivalent to re.ASCII). Please review: http://codereview.appspot.com/2439 Added file: http://bugs.python.org/file10998/reunicode5.patch ___ Python tracker <[EMAIL

[issue2834] re.IGNORECASE not Unicode-ready

Changes by Antoine Pitrou <[EMAIL PROTECTED]>: -- assignee: -> pitrou priority: -> critical ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue2834] re.IGNORECASE not Unicode-ready

Changes by Mark Summerfield <[EMAIL PROTECTED]>: -- nosy: +mark ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list mailing

[issue2834] re.IGNORECASE not Unicode-ready

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: http://codereview.appspot.com/2439 ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bu

[issue2834] re.IGNORECASE not Unicode-ready

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: This new patch adds re.ASCII in all sensitive places I could find in the stdlib (except lib2to3 which as far as I understand is maintained in a separate branch, and even has its own copy of tokenize.py...). Also, I didn't get an answer to the

[issue2834] re.IGNORECASE not Unicode-ready

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Improved patch which also detects incompatibilities for "(?u)". Added file: http://bugs.python.org/file10778/reunicode3.patch ___ Python tracker <[EMAIL PROTECTED]> _

[issue2834] re.IGNORECASE not Unicode-ready

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: This new patch also introduces re.ASCII as discussed on the mailing-list. Added file: http://bugs.python.org/file10777/reunicode2.patch ___ Python tracker <[EMAIL PROTECTED]>

[issue2834] re.IGNORECASE not Unicode-ready

Changes by Antoine Pitrou <[EMAIL PROTECTED]>: Added file: http://bugs.python.org/file10768/reunicode.patch ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue2834] re.IGNORECASE not Unicode-ready

Changes by Antoine Pitrou <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file10767/reunicode.patch ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue2834] re.IGNORECASE not Unicode-ready

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Here is a preliminary patch which doesn't remove re.LOCALE, but adds TypeError's for mistyped matchings, a ValueError when specifying re.UNICODE with a bytes pattern, and implies re.UNICODE for unicode patterns. The test suite runs fine after

[issue2834] re.IGNORECASE not Unicode-ready

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Le samedi 28 juin 2008 à 22:20 +, Guido van Rossum a écrit : > Finally, is there a use case of re.LOCALE any more? I'm thinking not. It's used for locale-specific case matching in the non-unicode case. But it looks to me like a bad practi

[issue2834] re.IGNORECASE not Unicode-ready

Guido van Rossum <[EMAIL PROTECTED]> added the comment: Sounds like re.UNICODE should be on by default when the pattern is a str instance. Also (per mailing list discussion) we should probably only allow matching bytes when the pattern is bytes, and matching str when the pattern is str. Finally

[issue2834] re.IGNORECASE not Unicode-ready

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Uh, actually, it works if you specify re.UNICODE. If you don't, the getlower() function in _sre.c falls back to the plain ASCII algorithm. >>> pat = re.compile('Á', re.IGNORECASE | re.UNICODE) >>> pat.match('á') <_sre.SRE_Match object at 0xb7

[issue2834] re.IGNORECASE not Unicode-ready

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Same here, re.LOCALE doesn't circumvent the problem. -- nosy: +pitrou ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue2834] re.IGNORECASE not Unicode-ready

Manuel Kaufmann <[EMAIL PROTECTED]> added the comment: I have the same error with the re.LOCALE flag... [humitos] [~]$ python3.0 Python 3.0a5+ (py3k:63855, Jun 1 2008, 13:05:09) [GCC 4.1.3 20080114 (prerelease) (Debian 4.1.2-19)] on linux2 Type "help", "copyright", "credits" or "license" for mo

[issue2834] re.IGNORECASE not Unicode-ready

Guido van Rossum <[EMAIL PROTECTED]> added the comment: Try adding re.LOCALE to the flags. I'm not sure why that is needed but it seems to fix this issue. I still think this is a legitimate bug though. -- nosy: +gvanrossum __ Tracker <[EMAIL PROTECTED]>

[issue2834] re.IGNORECASE not Unicode-ready

New submission from Sven Siegmund <[EMAIL PROTECTED]>: re cannot ignore case of special latin characters: Python 3.0a5 (py3k:62932M, May 9 2008, 16:23:11) [MSC v.1500 32 bit (Intel)] on win32 >>> 'Á'.lower() == 'á' and 'á'.upper() == 'Á' True >>> import re >>> rx = re.compile('Á', re.IGNORECAS