A new year, a new Python problem....

Hi all,
I’ve been using Linux for the last couple of years but as an end-user, not a tinkerer. This means that I use my distro’s prepackaged RPMs (Mandrake’s URPMI takes the hassle out of dependancy hell)
Of course, always having an up to date distro means that I have been woking with the latest Python i.e. 2.3.3
Some of the more complex scripts do not stand for this… (most others like tesselate however work great!)
Now Beast, which I wouldlike to try very much, does not work with 2.3.3…
Is there any way to install 2.2.3 next to 2.3.3 without breaking all the stuff depending on 2.3.3?
I won’t mind resetting the PYTHONHOME env var and the /usr/bin/python executable every time I start Blender, I just want that ‘old’ Python sandboxed…
Anyone have any pointers?

debian does this for you :wink:

you can install python’s side by side. i have /usr/lib/python2.{1-3}

i also see the blender makefiles.am use the python path @PYTHONPATHSOMETHING@/lib/python@PYTHONVERS@

( you dont need to be a programmer to work that out :wink: )

so i guess you just do that somehow. i would “presume” python source install would put it in the right place.

anyhow - get the source, study the configure directives