> As Chadrik mentioned it is a maya.OpenMaya bug, I am wondering how > many functions/methods influenced by this bug in Maya 8.5sp1?
i've circumvented the problem, but i had to disable undo for api-based methods on 8.5, since the crash was somehow related to intermixing maya.cmds with maya.OpenMaya. i'll take a closer look at a later time > It seems not to be a bug but it will be great to have this flexibility > to make __add__(), __sub__() and even __pow__() work as an object- > friendly way. got all this stuff working again. > The new treatment of non-existent objects took me a bit of time to get > used to/port my code. No big deal, and I don't mind the new behavior > at all - it makes sense to me. The bigger problem is that I have to > have all the tools ported and somewhat tested before I can release the > new version of pymel/tools to the studio. I would have much rather had > the feature be depreciated for one release to allow me more time to > transition smoothly. i added a '0_7_compatibility_mode' configuration option to get old- style treatment of non-existent objects. i'll post the new version shortly. thanks so much for all the feedback, guys. this is really helping to ensure that the release will be very stable. -chad > Because > that might be a big concern for me to decide upgrading pymel from 0.7 > to 0.9 or not. We are in rush hour such that I decided to delay > upgrading. --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/python_inside_maya -~----------~----~----~----~------~----~------~--~---
