(err... that should have read 'area', not 'are'...) - Paul
On Sat, Oct 2, 2010 at 1:21 PM, Paul Molodowitch <[email protected]> wrote: > For setAttr, it doesn't create a pynode... but the command is wrapped, so > it will still be slower than the maya.cmds equivalent. > In general, though, speed is one are where PyMel still has a lot of room > for improvement... > > - Paul > > On Sat, Oct 2, 2010 at 12:29 PM, breeder <[email protected]> wrote: > >> Example: >> import pymel.core as pm >> pm.setAttr("locator1.tx",5) >> >> So , in this example , does pymel use maya.cmds or is actually >> creating PyNode for "locator1" and than setting attribute??? >> >> >> >> >> On Oct 2, 8:16 pm, Jo Jürgens <[email protected]> wrote: >> > A node in maya.cmds is just a text string, while in Python it is a >> PyNode >> > instance. Creating all those instances in PyMel does take time. For >> > operations on large number of items where speed is crucial, I still tend >> to >> > use maya.cmds. >> >> -- >> http://groups.google.com/group/python_inside_maya >> > > -- http://groups.google.com/group/python_inside_maya
