M.-A. Lemburg wrote: > > Note that unicodedata is only needed by programs which do > a lot of Unicode manipulations and in the future probably > by some codecs too. Perhaps it would make sense to move the Unicode database on the Python side (write it in Python)? Or init the database dynamically in the unicodedata module on import? It's quite big, so if it's possible to avoid the static declaration (and if the unicodata module is enabled by default), I'd vote for a dynamic initialization of the database from reference (Python ?) file(s). M-A, is something in this spirit doable? -- Vladimir MARANGOZOV | Vladimir.Marangozov@inrialpes.fr http://sirac.inrialpes.fr/~marangoz | tel:(+33-4)76615277 fax:76615252
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