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, David Shaw <flopp...@gmail.com> wrote: > 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 <elron...@gmail.com> > wrote: >> >> 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 within >> it. >> To query your maya version even before maya.cmds has been populated, I >> recommend using MGlobal: >> >> from maya.OpenMaya import MGlobal >> >> apiVerNum = MGlobal.apiVersion() >> verString = MGlobal.mayaVersion() >> >> - Paul >> >> -- >> http://groups.google.com/group/python_inside_maya >> >> To unsubscribe, reply using "remove me" as the subject. > > -- > http://groups.google.com/group/python_inside_maya -- http://groups.google.com/group/python_inside_maya
