Note that there are some explanatory texts on larger screens.

plurals
  1. POEclipse environment for Maya's python modules
    primarykey
    data
    text
    <p>I'm trying to set up the Eclipse IDE to recognize the <strong>maya.cmds</strong> module, an all modules associated with the <strong>maya</strong> module. The following code are tests run in Eclipse, and Maya's script editor.</p> <pre><code>import maya print 'maya:\n', dir(maya) from maya import cmds print 'cmds:\n', len(dir(cmds)) # too many to print print 'sphere: ', cmds.sphere </code></pre> <p>In Maya's script editor the code results in</p> <pre><code>maya: ['OpenMaya', '_OpenMaya', '__builtins__', '__doc__', '__file__', '__name__', '__package__', '__path__', 'app', 'cmds', 'mel', 'standalone', 'stringTable', 'utils'] cmds: 3190 sphere: &lt;built-in method sphere of module object at 0x0000000019F0EEE8&gt; </code></pre> <p>In Eclipse the code results in</p> <pre><code>maya: ['__builtins__', '__doc__', '__file__', '__name__', '__package__', '__path__'] cmds: 6 sphere: Traceback (most recent call last): AttributeError: 'module' object has no attribute 'sphere' </code></pre> <p>I've done a lot of searching, on the google group "python inside maya", and web searches. The best I've found was the following link, however this did not solve my issue at all, and in the end gave the same result. <a href="http://www.luma-pictures.com/tools/pymel/docs/1.0/eclipse.html" rel="nofollow">http://www.luma-pictures.com/tools/pymel/docs/1.0/eclipse.html</a></p> <p>I've read that I should be setting my environment paths in Eclipse, rather than my machine, and I've also read the opposite opinion. What environment vars should I set, to where, and in Eclipse, Windows, or both?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload