We use a minimal sitecustomize.py, but it's intentionally minimal - it
just copies data from a buffer var into PYTHONPATH. We don't use the
maya.env file at all because we need all of our tools to run from
similarly configured environments. We do this with data from xml
files. We also do not use th
I use a sitecustomize.py for our general python packages and a
seperate usersetup.py (right beside the sitecustomize.py) to handle
specific items for maya.
It cuts down the sitecustomize into more manageable pieces and seems
to be working out well for us.
Ian
On Sun, Apr 11, 2010 at 8:06 PM, Da
Thank you Paul, much appreciated.
Do you think the approach I am taking is feasible or practical?
How do you guys go about it?
Dave
On Mon, Apr 12, 2010 at 1:55 AM, Paul Molodowitch wrote:
> In a nutshell - yes, it's probably failing because cmds hasn't been
> properly initialized yet.
> The
Do the pymel installs build on one another i.e do I need 0.9.2 and 1.0.1 to
have all access to all the pymel functions?
On Wed, Apr 7, 2010 at 9:15 AM, shawnpatapoff wrote:
> Excellent, thank you very much.
>
> On Apr 7, 12:13 am, Ofer Koren wrote:
> > pymel functions are equivalent to maya.cmds
Hey JP,
Pretty slick, I haven't animated with it but the first intital test seemed
to work pretty well. So I am trying to cut my teeth with classes and
instances when and where to best utilize class functions. Did you discover
resaons or have suggestions "WHY to create classes, WHEN to
create them
In a nutshell - yes, it's probably failing because cmds hasn't been
properly initialized yet.
The deal with maya.cmds is that's it's actually an empty module, whose
contents are filled in during maya's initialization process. That's
why you were able to import it, but not call anything useful with
Hey folks,
I've setup a sitecustomize.py script which is located in a Maya module path
to customise our Maya setup on launch
It basically queries a custom Maya environment variable located in the *
maya.env* called "*PYTHON_SITEPACKAGES*" with
the following path: "*D:/pipeline_tools/python/site-p
