On Wed, 2006-01-04 at 09:04 -0800, Donnie Berkholz wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Patrick Lauer wrote: > | Hi all, > | > | I recently ran into an interesting problem: > | > | One app I have seems to trigger a bug in Python 2.4, so I want to use it > | with Python 2.3 > | But, as it imports a few python modules I can't use it - the modules > | only get installed to the most recent Python version. > | > | From a portage dependency p.o.v it is satisfied - $program needs Python > | 2.3 and (among others) PyCrypto, but PyCrypto is only available in > | Python 2.4 and fails to import in 2.3 > | > | Now I'm wondering - is there a sane way of handling this that doesn't > | forcefully remove python 2.4? > | e.g. could python modules be installed to multiple python versions? How > | do others (ruby, perl, ...) handle it? For the moment I've "solved" that > | by package.masking python 2.4, unmerging it and rebuilding all Python > | modules - less than optimal ... > > Many programs have configure options for where the python module > directory is, or which python version they're using. If not, move the > files around manually in src_install(). > > sci-chemistry/sparky installs for python 2.3 only. That won't solve the basic problem - how would I be able to have programs using Python 2.3 and Python 2.4 at the same time? Also, having to manually fiddle with the almost 60 packages depending on Python on my system doesn't seem very useable to me ...
Still, thanks for the input, Patrick -- Stand still, and let the rest of the universe move
signature.asc
Description: This is a digitally signed message part
