On Sat, Jun 19, 2004 at 02:04:11PM +0200, "Martin v. L?wis" wrote:
Hye-Shik Chang wrote:
Okay. But how about embedded, freezed environments or statically compiled into python by uncommenting from Modules/Setup? If somebody need to support only legacy Japanese encodings, he will want to include a legacy mapping(70K) but will not want JIS X 0213(85K) and KS X 1001, GB2312 mappings(200K, for iso-2022-jp-2).
People who want that have many options: the could go back to an older version of CJKCodecs, they could use Japanese codecs, they could write their own codecs based on libraries that are only available to the embedded Python, they could break down your modules again.
For the average user, it does not matter much. For packaging and maintaining, I believe it is slightly simpler to have fewer files.
Yeah. I just finished merging varities of codecs into few per-locale modules. before after (codecs+maps) _codecs_cn.so 159851 130769 _codecs_jp.so 340350 241307 _codecs_kr.so 150269 125508 _codecs_tw.so 110057 97567 _codecs_unicode.so 17050 12332 _multibytecodec.so 24438 24439 802015 631922 As a result, 166KB is saved by this unification. And, I guess that builtin codec initialization time in Windows may be saved also. :) Hye-Shik