Took longer than I thought to fix, mostly due to some strange inconsistencies (for instance, did anyone know that it's possible to have transform node types that aren't compatible with MFnDagNode?), but I pushed out a new version to github that should resolve these issues.
One caveat - it currently doesn't support any versions prior to 2011. Our official policy is to support the last 3 versions of maya - which right now would be 2013, 2012, and 2011 - but if enough people want, I can try to find a copy of 2010 or whatever and see about making it compatible with that. Also, it's hot off the presses - it passes our unittest suite, which is fairly extensive, so it should be stable... but it hasn't been tested "out in the wild" yet, so buyer beware. =) - Paul On Wed, Oct 10, 2012 at 8:55 PM, Chad Vernon <[email protected]> wrote: > We're using Maya 2012 vanilla default pymel. We can't update as this is > on our client's systems who are the ones reporting the crashing, but we'll > pass along the info. Thanks. > > > On Wed, Oct 10, 2012 at 6:52 PM, Farsheed Ashouri < > [email protected]> wrote: > >> We have same problem in our projects. >> >> >> On Thursday, October 11, 2012, Paul Molodowitch wrote: >> >>> Hey chad - I'm actually currently working on an update to pymel which >>> addresses these issues - should be out on github in the next day or two. >>> >>> A couple questions: >>> >>> a) What version of maya are you using? >>> b) Are you using a "custom" pymel install (pulling from our github >>> repo), or are you using the version built into maya? >>> c) If you're just using the default maya install of pymel, is there any >>> possibility of installing / using a version pulled from github? >>> >>> In the meantime, you can try monkey-patching >>> pymel.core._addPluginNode(pluginName, mayaType) so that it does nothing... >>> Should definitely only be used a temporary fix though - it will mean that >>> any new nodes from your plugin will just be treated as a 'DependNode' - and >>> can create some strange situations where doing: >>> >>> objectType('myCustomTransform1', isAType='transform') >>> >>> >>> will return different results than: >>> >>> isinstance(pm.PyNode('myCustomTransform'), pm.nt.Transform) >>> >>> >>> For some background: >>> >>> When a plugin loaded, pymel needs to check if that plugin provides any >>> new node types, and if so, query some basic information about the nodes, so >>> it knows how to create a new PyNode class to wrap it. Prior to maya2012, >>> the only way to get inheritance information about a node type was by >>> actually creating an instance of that node... so it was a dirty little >>> secret that pymel actually created and then destroyed instances of those >>> nodes just so it could query inheritance. >>> This was obviously not a great solution, though, so we got Autodesk to >>> include OpenMaya.MNodeClass / cmds.nodeType(isTypeName) in 2012, so now we >>> can get the information we need without needing to actually create nodes. >>> However, it seems there were some holes that's causing these ghost nodes to >>> still being created, so I'm looking to patch these up. >>> >>> - Paul >>> >>> On Wed, Oct 10, 2012 at 4:44 PM, Chad Vernon <[email protected]>wrote: >>> >>>> It looks like Pymel has some callbacks that monitor plug-in loading. >>>> Is there a way to disable this as it conflicts with some of our plug-ins >>>> and is causing our scenes to crash. >>>> >>>> Thanks, >>>> Chad >>>> >>>> -- >>>> view archives: http://groups.google.com/group/python_inside_maya >>>> change your subscription settings: >>>> http://groups.google.com/group/python_inside_maya/subscribe >>>> >>> >>> -- >>> view archives: http://groups.google.com/group/python_inside_maya >>> change your subscription settings: >>> http://groups.google.com/group/python_inside_maya/subscribe >>> >> >> >> -- >> Sincerely, >> Farsheed Ashouri, >> ourway.ir >> Tel: +98 9388801504 >> >> -- >> view archives: http://groups.google.com/group/python_inside_maya >> change your subscription settings: >> http://groups.google.com/group/python_inside_maya/subscribe >> > > -- > view archives: http://groups.google.com/group/python_inside_maya > change your subscription settings: > http://groups.google.com/group/python_inside_maya/subscribe > -- view archives: http://groups.google.com/group/python_inside_maya change your subscription settings: http://groups.google.com/group/python_inside_maya/subscribe
