Hi there,

has anyone running blender with python 2.4 on Slack current? Here nor the
version form blender.org neither the package from linuxpackages (10.0
version) does work, always complains about missing python. As I read that
blender depends on python 2.3 I created smylinks to 2.4 and named them 2.3
but that doesn't work.

Any hints for me? TIA

--
Cheerz Lars

Lars Behrens wrote:
> Hi there,
>
> has anyone running blender with python 2.4 on Slack current? Here nor the
> version form blender.org neither the package from linuxpackages (10.0
> version) does work, always complains about missing python. As I read that
> blender depends on python 2.3 I created smylinks to 2.4 and named them 2.3
> but that doesn't work.
>
> Any hints for me? TIA
>
> --
> Cheerz Lars

Set your python path according to the instructions located here:

http://download.blender.org/document...lI/c11855.html

(Scroll down to the part that says "Setting PYTHONPATH on Linux and
other UNIXes")

Chris Sorenson wrote:

> Set your python path according to the instructions located here:
>
> http://download.blender.org/document...lI/c11855.html
>
> (Scroll down to the part that says "Setting PYTHONPATH on Linux and
> other UNIXes")

Thanks for your advice! I followed the instructions but still no luck.
Blender started but without gui, prompting "'import site' failed; use -v
for traceback" so I decided to try the static version form blender.org and
now it works (though that error message is still there).

--
Cheerz Lars

Lars Behrens wrote:
>
> Thanks for your advice! I followed the instructions but still no luck.
> Blender started but without gui, prompting "'import site' failed; use -v
> for traceback" so I decided to try the static version form blender.org and
> now it works (though that error message is still there).
>

Having just taken a quick look at google groups, I see that that
particular python error is not an easy one to track down. Perhaps you
might want to try using the python from slack 10.1 instead of
slack-current...

Chris Sorenson wrote:

> Having just taken a quick look at google groups, I see that that
> particular python error is not an easy one to track down. Perhaps you
> might want to try using the python from slack 10.1 instead of
> slack-current...

Having taken a quick look at google groups myself, I decided to ignore it
until it bugs in any way during work. ;-)

--
Cheerz Lars