On Sat, Oct 9, 2010 at 3:25 PM, Scott Kitterman <[email protected]> wrote: > On Friday, October 08, 2010 11:28:53 pm Mackenzie Morgan wrote: >> On Friday, October 08, 2010 03:55:04 am Matthias Klose wrote: >> > On 07.10.2010 22:19, Barry Warsaw wrote: >> > > As a policy, I do think it makes sense for us to have one Python >> > > version overlap between LTS releases. >> > >> > Are there concrete examples of these applications for end users (no, I >> > wouldn't count Launchpad to to it ;). >> > >> > 20MB are 2% of the CD space, and I suppose an end user would care more >> > about shipping something useful like a language pack, another >> > application, but not a bunch of unused python modules. >> >> So don't put it on the cd, but keep in in the archive. That way, if they >> need it for compatibility, they can get it, but it's not wasting space for >> the general case. > > Python extensions are built for each supported Python version, so having two > supported versions doubles the number of Python extension .so files on the CD. > These are part of the same binary package and so there's no convenient way to > separate them out.
Oh. I thought the issue was just the python2.6 package :-/ -- Mackenzie Morgan http://ubuntulinuxtipstricks.blogspot.com apt-get moo -- ubuntu-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
