On Wednesday 12 November 2003 18:46, Alastair Tse wrote:
> I need some more testing for python-2.3.2 before it is released into
> ~x86.
This update is looking good here. Fine work. 8)
> 2. run: emerge -u portage python
note that -u will update alot of things with ~x86 that you might not want.
> UCS4 uses significantly more memory than UCS2.
I have compared ucs2 (with the ebuild in portage) and ucs4 (with hacking that
ebuild to include the --enable-unicode=ucs4 configure switch). I compared:
1. The sizes of a newly started interpreter using the RES column on 'top'
2. The size of a "btdownloadheadless" process seeding a knoppix cd image
3. The size of the .tbz2 binary package.
The empty interpreters are of identical size. The bittorrent process is
considerably *smaller* with ucs4, and the tbz2 files are largely unchanged in
size. Numbers below. IMHO thats a clear but suprising win for ucs4. Lets use
it always.
> Plan for Python's Future
> ========================
Portage has a number of packages that still need 2.2 but reference
#!/usr/bin/python. For example, rdiff-backup. The distutil eclass has support
for forcing /usr/bin/python2.1 (thanks to zope), but I cant see any way to
force 2.2. am I overlooking something?
ucs2 ucs4
empty interpreter 2928 2928
btdownloadheadless 6076 5464, 5420
tbz2 size 5954517 5951807
--
Toby Dickenson
--
[EMAIL PROTECTED] mailing list
