My understanding is that sitecustomize.py is still supported, just not
in all the ways it used to be prior to version 2.5. I'm using it with
version 2.6 right now in fact.
The major change in 2.5 related to sitecustomize.py is that it must be
on the original pythonpath in order for it to be execut
Just be aware that sitecustomize.py is unsupported by Python since Python 25
and may cause problems with other modules. Ive had it break Django or Pylons
(dont remember which one), so I stopped using it.
On Mon, Apr 12, 2010 at 8:41 AM, Judah Baron wrote:
> We use a minimal sitecustomize.py, b
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
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
