How to call python2.5 in houdini 12?

   4116   4   3
User Avatar
Member
4 posts
Joined: Aug. 2012
Offline
In the Windows operating system,houdini12 uses python2.6,but now I need to call python2.5, Is there somebody knows how to do this?
And what are the detailed steps to do this?
It will be greatly appreciated for your help.
Thanks again!
User Avatar
Member
7717 posts
Joined: July 2005
Online
$ hconfig -h HOUDINI_PYTHON_LIB
HOUDINI_PYTHON_LIB
The Python library that Houdini should load at startup. By default,
Houdini searches for a suitable Python library in the system's
standard locations and falls back to the library in $HFS if none
can be found. Setting this variable overrides that behaviour.


EDIT: I think you give it a path to the python25.dll
User Avatar
Member
4 posts
Joined: Aug. 2012
Offline
edward
$ hconfig -h HOUDINI_PYTHON_LIB
HOUDINI_PYTHON_LIB
The Python library that Houdini should load at startup. By default,
Houdini searches for a suitable Python library in the system's
standard locations and falls back to the library in $HFS if none
can be found. Setting this variable overrides that behaviour.


EDIT: I think you give it a path to the python25.dll

Thank you very much, edward !!
I am trying to work it out now.I really appreciate your help.
Thanks a million times.
User Avatar
Member
100 posts
Joined: Nov. 2010
Offline
Is there a reason why Houdini doesn't use Python 3.x?
User Avatar
Member
21 posts
Joined: Sept. 2011
Offline
hopbin9
Is there a reason why Houdini doesn't use Python 3.x?

My understanding is because most studios' pipelines are glued together with python scripts that were written years ago and converting python scripts from 2.x to 3.x can be more than trivial. It is the same reason that Maya's shipped python version is a similar one to Houdini's, and why I'm pretty sure PRMan's python bindings only work with 2.x, etc.. Once larger studios move to 3.x, so will Houdini, along with every other major CG package.

If you write your python scripts intelligently by never using deprecated features and using “from __future__ import (replacement feature X)” as much as possible, your scripts should be fairly easy to convert when the time comes that 3.x is supported.
  • Quick Links