On Tue, Nov 30, 2010 at 8:38 AM, Antoine Pitrou <solipsis at pitrou.net> wrote:
> On Mon, 29 Nov 2010 22:46:33 -0500
> Alexander Belopolsky <alexander.belopolsky at gmail.com> wrote:
>>
>> In practical terms, UCD comes at a price. The unicodedata module size
>> is over 700K on my machine. This is almost half the size of the
>> python executable and by far the largest extension module. (only CJK
>> encodings come close.) Making builtins depend on the largest
>> extension module for operation does not strike me as sound design.
>
> Well, do they depend on it? _PyUnicode_EncodeDecimal seems to depend
> only on Objects/unicodectype.c.
My mistake. That was a late night post. I wonder why unicodedata.so
is so big then.
It must be character names:
$ python -v
>>> '\N{DIGIT ONE}'
dlopen("/.../unicodedata.so", 2);
import unicodedata # dynamically loaded from /.../unicodedata.so
'1'
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