[wingide-users] Source analysis of maya.cmds package?

[Eric Pavey]

This is a question specific to the scripting language of the the DCC app
Maya.  I'm trying to get Wing to do source analysis of it's
*maya.cmds*package.  After finding these threads online, and working
through them, I
have been able to get its* maya.OpenMaya* package working successfully:

   - http://wingware.com/pipermail/wingide-users/2008-May/005398.html
   -
   http://groups.google.com/group/python_inside_maya/browse_thread/thread/8f0923d15747aa8e?pli=1

And have posted my results here (which includes some of my work on the topic
below):

   - http://mayamel.tiddlyspot.com/#[[Source%20Analysis%20in%20Wing]]

However, how Maya deals with it's maya.cmds package is very different than
its maya.OpenMaya package.  It seems to generate it upon launch... there is
no physical package on disk to inspect.  I've described what its' doing on
my blog here:

   - http://www.akeric.com/blog/?p=828

I've been able to generate a (seemingly) appropriate .pi file for the
maya.cmds package via this code (by having Maya's python executable running
in Wing):

import maya.cmds as mc

filepath = 'c:/temp/cmds.pi'
f = open(filepath, mode='w')

for k in sorted(mc.__dict__.keys()):
    f.write('def %s():\n'%k)
    f.write('    pass\n')
    f.write('\n')
f.close()

And I've put this .pi file in the same location as the OpenMaya ones.  But
Wing currently isn't detecting it for source analysis.

Any thoughts\help?

thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: /pipermail/wingide-users/attachments/20100111/2c51d525/attachment.html