I found that using usersetup.py proves to be problematic more that useful.
What I do is create a mayaInit.py with all the pretty python code.
Then use the good old try-tested-and-true userSetup.mel that call my
mayaInit.py using the command
python("import mayaInit as mi;mi.mayaInit()")
This prove to be more robust. I never really knew when the usersetup.py was
executed, but the mel counterpart is always excuted quite early in the
loading process, so i`m sure my init code is running when I expect it to.
Hope this helps somehow.
Sylvain Berger
On Fri, Mar 12, 2010 at 6:22 PM, Chad Dombrova <[email protected]> wrote:
> what version of pymel? you could try setting the pymel logger to debug
> mode. there .conf file should be in the pymel install directory. you can
> also control it with an environment variable. check the conf file for
> details.
>
> -chad
>
>
>
>
> On Fri, Mar 12, 2010 at 3:01 PM, Judah Baron <[email protected]> wrote:
>
>> When I run pymel our userSetup.py file is not run, which means none of our
>> tools run. This appears to be happening only on my machine, and it just
>> started happening the other day. It is also happening only with interactive
>> Maya. As part of our startup process we run a copy of Maya standalone and
>> that calls userSetup as expected.
>>
>> I've reverted all of my local changes and am now running the same set of
>> files that another developer here is running. The difference is that his
>> userSetup file gets called and mine does not. I've also re-installed pymel
>> and Maya.
>>
>> I feel like I've just stepped into the twilight zone. If someone can shed
>> any light on this I would greatly appreciate it.
>>
>> thanks,
>> -Judah
>>
>> --
>> http://groups.google.com/group/python_inside_maya
>
>
> --
> http://groups.google.com/group/python_inside_maya
>
--
http://groups.google.com/group/python_inside_maya
