Summary: | making python packages available for all major versions of python | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Tobias Brox <tobias> |
Component: | New packages | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED WORKSFORME | ||
Severity: | enhancement | CC: | coldwind, crquan, dubnerm, luckyluke, zlin |
Priority: | Lowest | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Tobias Brox
2005-07-21 12:42:12 UTC
A variation of this is a recent emerge -u world does now pick up new python, but does not auto pick up psycopg library. I use python as cgi script and took awhile to sift through and realize I needed to re-emerge psycopg. But reemerge of psycopg fails because you first have to reemerge egenix-mx-base for psycopg. Would have been nice, if at all possible, for the python upgrade to auto pick up reemerge of secondary libs, and in the correct sequence. unfortunately, its is a limitation of the packaging system that we can't do this cleanly. the kernel modules side of things has a workable scheme, i believe. so it might be benefitial to look into that. Portage comment: You don't want the kernel module solution (it's a hardcoded CONFIG_PROTECT extension in portage itself), it's not very nice from both implementation and user POV. thanks for the comment from genone. i'm going to keep this open, but its going to be something we will think aboiut further down the track. everyone should benefit from having the latest supported version of python running. this is Oct 2007 now, is there some new improvements now? I have encountered a similar problem as this: I use python2.4, and then installed a python2.5 SLOT, the python-updater could upgrade all my python modules to python2.5, but when I use zope and plone, it needs python2.4 and a specific python module, at this time this specific module is only available to my python2.5, I don't know how to make it available to python2.4 just by emerge and portage approach, I have to install the specific pymodule with 'python2.4 setup.py install' command, that sounds not good. It would be nice if we can have same package in different python versions simulateneusly. In current scheme we could try to rewrite SLOTS in python eclasses. So if package ebuild have no SLOTS it got them from python, if it have any it got slots for every pair of python-slot and package-slot. I.e. if package have (in different ebuilds of cause): SLOT="2" SLOT="3" we create slots: SLOT="2:2.3" SLOT="2:2.4" SLOT="2:2.5" SLOT="3:2.3" SLOT="3:2.4" SLOT="3:2.5" This scheme can also be useful for other plugin systems - i.e. xulrunner applications, firefox addons, postgresql package libraries and so on. Any ideas how this can be done? Hi, There's another way to do that : # emerge app-admin/eselect-python # eselect python list Available python interpreters: [1] python2.4 [2] python2.5 * # eselect python set python2.4 # emerge dev-python/psycopg ==> Installation in : /usr/lib/python2.4/site-packages/psycopg2 maybe, this can help. Best regards. |