Ezio Melotti <[email protected]> added the comment:
Attached a new patch that adds support for named sequences (still needs some
test and can probably be improved).
> There are certainly advantages to that strategy: you don't have to
> deal with [\N{sequence}] issues.
I assume with [] you mean a regex character class, right?
> If the argument to unicode.lookup() and be any of name, alias, or
> sequence, that seems ok.
With my latest patch, all 3 are supported.
> \N{} should still do aliases, though, since those don't have the
> complication that sequences have.
\N{} will only support names and aliases (maybe this can go in 2.7/3.2 too).
> You may wish unicode.name() to return the alias in preference,
> however. That's what we do. And of course, there is no issue of
> sequences there.
This can be done for 3.3, but I wonder if it might create problems. People
might use unicodedata.name() to get a name and use it elsewhere, and the other
side might not be aware of aliases.
----------
Added file: http://bugs.python.org/file23280/issue12753-2.diff
_______________________________________
Python tracker <[email protected]>
<http://bugs.python.org/issue12753>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
