Posting for Drew Skillman of DoubleFine from tech-artists.org forum:

"We're running into some trouble with the new deployment scheme for
1.0. Specifically, pymel now needs to be imported prior to the maya
libs, which means it needs to appear before those maya libs in
sys.path.

This is actually tricky to accomplish if you already have PYTHONPATH
defined as an environment variable, and aren't in a position to change
it. This is because if PYTHONPATH is defined, adding it to the
maya.env does nothing (i'm using maya 2008 and carefully verified
this).

I can move the 2 necessary PyMel folders into the folder that's
currently defined in PYTHONPATH, but that's pretty ugly since our maya
tools are supposed to live elsewhere (not to mention the confusion of
having those 2 folders piled in with a bunch of other modules).

So my question for you guys is does anyone know another way to get
PyMel added to the system paths before the standard maya libs, without
relying on PYTHONPATH (or hacking the maya install itself)."

Any help would be appreciated, I'll post response in other forum if
anybody has a good solution.

-jason
-- 
http://groups.google.com/group/python_inside_maya

Reply via email to