Issue 137 in pymel: PyMel 1.0 beta install
codesite...@google.com
Owner: ----
New issue 137 by tryptik: PyMel 1.0 beta install
http://code.google.com/p/pymel/issues/detail?id=137
Hi, all. My name is John Hood and I am working at SONY Imageworks. I
would like to evaluate the new beta for use here. Unfortunately, our Maya
launcher makes it difficult to order the python paths properly so that the
PyMel modules are sourced before the Maya site packages. Is there any way
to get around this? A cursory examination of the assert indicates
potential incompatibility with the logging module - can that be omitted?
I apologize if this is the wrong place to present this issue - I wasn't
sure how to contact you.
Thanks
-J
What Version of Maya are you using? On what operating system? (Please be as
specific as possible and include service packs, 64bit vs 32bit, etc)
We are using Maya 2009 on linux 64-bit os.
What Version of PyMEL are you using?
Trying pymel-1.0.0b2.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
codesite...@google.com
Comment #1 on issue 137 by chadrik: PyMel 1.0 beta install
http://code.google.com/p/pymel/issues/detail?id=137
hi john,
the new maya module fixes 3 things:
* allows you to use PyMEL inside userSetup.py in python standalone
* fixes a bug where certain commands don’t return a result the
first time they
are called
* provides a shared root logger with status-line error and warning
colorization
proceeding without the custom maya package would be tricky. unless we hear
the
same complaint from many users i don't think that it will be a priority to
edit pymel
to work without it. however, you are welcome to fork pymel and make the
modifications. our repo is here: http://github.com/LumaPictures/pymel. just
be
aware there is a *chance* we might change the location.
codesite...@google.com
Comment #2 on issue 137 by elrond79: PyMel 1.0 beta install
http://code.google.com/p/pymel/issues/detail?id=137
John - what, exactly, about your maya launcher makes it difficult to order
the python
paths? Does it re-order existing entries already present in sys.path? Or
does it
simply find and add modules in effectively random order onto the start/end
of the
maya path? At what point in the load process does it do this?
Did you try using a 'setuptools'-style .pth file? Ie, a .pth file with this
code
inserted into it:
import sys; sys.__plen = len(sys.path)
path/To/Pymel
import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:];
sys.path[0:0]=new
Alternatively, you can always simply overwrite the files that come with
maya with the
versions included in pymel; the pymel ones were written so that they should
be
completely compatible, even if pymel isn't loaded... they essentially just
add some
'extra' capabilities/options, which pymel makes use of.