public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alastair Tse <liquidx@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] python-2.3.2 testing required
Date: Fri, 14 Nov 2003 09:37:04 +0000	[thread overview]
Message-ID: <1068802623.11049.34.camel@huggins.eng.cam.ac.uk> (raw)
In-Reply-To: <200311132334.28834.tdickenson@devmail.geminidataloggers.co.uk>

[-- Attachment #1: Type: text/plain, Size: 2246 bytes --]

On Thu, 2003-11-13 at 23:34, Toby Dickenson wrote:
> > 2. run: emerge -u portage python
> 
> note that -u will update alot of things with ~x86 that you might not want. 
> 

True, although in theory, it works also if you mark them as stable. I've
been running python-2.3 on a stable box without any problems. YMMV.

> > 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.

That is rather suprising. I could only explain that by predicting that
btdownloadheadless doesn't use any unicode objects at all. As I said
before, I think the real test case would be XML parsing.

But hopefully this weekend I could formulate some tests to run to get
something more "scientific". But it might be that my initial
observations were off.

> 
> > 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?

Zope is a special case because it is not supported if you run it on
anything about 2.1. I'm not too familiar with Zope, so maybe some others
can chime in. As for packages that don't work with 2.3, that needs to be
fixed. There is a bug open now that people can report apps that don't
work with 2.3 either because 2.2 is hardcoded or they just need to be
patched.

http://bugs.gentoo.org/show_bug.cgi?id=33372

Cheers,
-- 
Alastair 'liquidx' Tse
 >> Gentoo Developer
 >> http://www.liquidx.net/ | http://dev.gentoo.org/~liquidx/


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-11-14  9:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-12 18:46 [gentoo-dev] python-2.3.2 testing required Alastair Tse
2003-11-13  8:07 ` Nick Jones
2003-11-13  9:57   ` Alastair Tse
2003-11-13  8:07 ` Alastair Tse
2003-11-13  9:05 ` Paul de Vrieze
2003-11-13  9:38   ` Alastair Tse
2003-11-13  9:10 ` Toby Dickenson
2003-11-13  9:51   ` Alastair Tse
2003-11-13 23:34 ` Toby Dickenson
2003-11-14  9:37   ` Alastair Tse [this message]
2003-11-15  8:09 ` Simon Watson
2003-11-17  0:29 ` Alastair Tse
2003-11-17 10:28   ` Toby Dickenson
2003-11-17 10:48     ` Alastair Tse

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1068802623.11049.34.camel@huggins.eng.cam.ac.uk \
    --to=liquidx@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox