Closed GoogleCodeExporter closed 9 years ago
this issue should probably just be marked as 'invalid' or 'as designed' or
whatever
tag you're using to flag non-issues.
just remembered that all the nodes are subclasses of pythons unicode, and as
such are
immutable, and then recalled reading the section on 'Immutability' in the docs
referring to the pymel module itself. RTFM.
assigning the output of rename() to a variable does indeed work as advertised.
my bad.
Original comment by john.d.b...@gmail.com
on 11 Apr 2008 at 9:17
in the next version pymel, pynode types will no longer be based on unicode, but
on a new object based
around the api MObject. the decision ensures the longevity and legitimacy of
this project, because it initiates
the marriage of maya.cmds and the api, which with the advent of python in maya,
is an arbitrary distinction
inherited from mel (so long as one is not making nodes or commands). in the
short run, there may be a
performance hit because maya.cmds functions will need to stringify our pymel
MObject nodes. however, we
are in talks with autodesk and have conveyed to them the tremendous advantage
of making maya.cmds
"MObject-aware", so with future versions of maya, and with pymel's own custom
listing commands, you will
see 100-fold performance gains. also, it solves your immutability quandary. :)
for more on what autodesk can do to improve python in maya:
http://code.google.com/p/pymel/wiki/Autodesk
Original comment by chad...@gmail.com
on 12 Apr 2008 at 5:07
Original comment by chad...@gmail.com
on 10 Feb 2009 at 7:42
Original issue reported on code.google.com by
john.d.b...@gmail.com
on 4 Apr 2008 at 7:57