| 1 |
On Wed, 2006-01-04 at 09:04 -0800, Donnie Berkholz wrote: |
| 2 |
> -----BEGIN PGP SIGNED MESSAGE----- |
| 3 |
> Hash: SHA1 |
| 4 |
> |
| 5 |
> Patrick Lauer wrote: |
| 6 |
> | Hi all, |
| 7 |
> | |
| 8 |
> | I recently ran into an interesting problem: |
| 9 |
> | |
| 10 |
> | One app I have seems to trigger a bug in Python 2.4, so I want to use it |
| 11 |
> | with Python 2.3 |
| 12 |
> | But, as it imports a few python modules I can't use it - the modules |
| 13 |
> | only get installed to the most recent Python version. |
| 14 |
> | |
| 15 |
> | From a portage dependency p.o.v it is satisfied - $program needs Python |
| 16 |
> | 2.3 and (among others) PyCrypto, but PyCrypto is only available in |
| 17 |
> | Python 2.4 and fails to import in 2.3 |
| 18 |
> | |
| 19 |
> | Now I'm wondering - is there a sane way of handling this that doesn't |
| 20 |
> | forcefully remove python 2.4? |
| 21 |
> | e.g. could python modules be installed to multiple python versions? How |
| 22 |
> | do others (ruby, perl, ...) handle it? For the moment I've "solved" that |
| 23 |
> | by package.masking python 2.4, unmerging it and rebuilding all Python |
| 24 |
> | modules - less than optimal ... |
| 25 |
> |
| 26 |
> Many programs have configure options for where the python module |
| 27 |
> directory is, or which python version they're using. If not, move the |
| 28 |
> files around manually in src_install(). |
| 29 |
> |
| 30 |
> sci-chemistry/sparky installs for python 2.3 only. |
| 31 |
That won't solve the basic problem - how would I be able to have |
| 32 |
programs using Python 2.3 and Python 2.4 at the same time? Also, having |
| 33 |
to manually fiddle with the almost 60 packages depending on Python on my |
| 34 |
system doesn't seem very useable to me ... |
| 35 |
|
| 36 |
Still, thanks for the input, |
| 37 |
|
| 38 |
Patrick |
| 39 |
-- |
| 40 |
Stand still, and let the rest of the universe move |
Archives