It's probably just me, but the names of the two unicode
modules tend to irritate me:
> ls u*.pyd
ucnhash.pyd unicodedata.pyd
(the former contains names, the latter data)
I've been meaning to rename the former, but I just realized
that it might be better to get rid of it completely, and move
its functionality into the unicodedata module.
The result is a single 200k unicodedata module, which con-
tains the name database as well as two new functions:
name(character [, default]) => map unicode
character to name. if the name doesn't exist,
return the default object, or raise ValueError.
lookup(name) => unicode character
(or raise KeyError if it doesn't exist)
Should I check it in now, change the names/semantics and check
it in, or post it to sourceforge?
Cheers /F
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4