Vlastimil Brom <[email protected]> added the comment:
Thanks for the quick update,
I confirm the fix for both issues;
just another finding (while testing the behaviour mentioned previously -
msg91917)
The property name normalisation seem to be much more robust now, I just
encountered an encoding error using a rather artificial input (in python 2.5,
2.6):
>>> regex.findall(ur"\p{UppercaseÄÄÄLetter}", u"QW\p{UppercaseÄÄÄLetter}as")
Traceback (most recent call last):
File "<pyshell#4>", line 1, in <module>
regex.findall(ur"\p{UppercaseÄÄÄLetter}", u"QW\p{UppercaseÄÄÄLetter}as")
File "C:\Python25\lib\regex.py", line 213, in findall
return _compile(pattern, flags).findall(string, overlapped=overlapped)
File "C:\Python25\lib\regex.py", line 599, in _compile
parsed = _parse_pattern(source, info)
File "C:\Python25\lib\regex.py", line 690, in _parse_pattern
branches = [_parse_sequence(source, info)]
File "C:\Python25\lib\regex.py", line 702, in _parse_sequence
item = _parse_item(source, info)
File "C:\Python25\lib\regex.py", line 710, in _parse_item
element = _parse_element(source, info)
File "C:\Python25\lib\regex.py", line 837, in _parse_element
return _parse_escape(source, info, False)
File "C:\Python25\lib\regex.py", line 1098, in _parse_escape
return _parse_property(source, info, in_set, ch)
File "C:\Python25\lib\regex.py", line 1240, in _parse_property
raise error("undefined property name '%s'" % name)
error: <unprintable error object>
>>>
Not sure, how this would be fixed (i.e. whether the error message should be
changed to unicode, if applicable).
Not surprisingly, in python 3.1, there is a correct message at the end:
regex.error: undefined property name 'UppercaseÄÄÄLetter'
vbr
----------
_______________________________________
Python tracker <[email protected]>
<http://bugs.python.org/issue2636>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
