So what seems to be happening is that pymel.core.general.spaceLocator has been altered to return just a Locator and not a list. pymel.core.nodetypes.Locator uses pymel.core.general.spaceLocator to generate the object, and then because it isn't a list (which is what the generic pymel machinery expects) it throws that error.
So this is definitely a bug. On Friday, November 2, 2018 at 6:03:14 PM UTC-5, Luca Di Sera wrote: > > I can't seem to find anything about this particular problem on the web. > Basically, If I create a locator in any other way or if I instantiate any > other pymel.core.nodetype.* class ( I haven't tried them all obviously ) I > incur in no unexpected behavior. > If I, instead, try to create an instance of the > pymel.core.nodetypes.Locator class, I incur in the following error : > > > # Error: line 1: ValueError: file C:\Program > Files\Autodesk\Maya2017\Python\lib\site-packages\pymel\core\general.py line > 2273: unexpect result locator1 returned by spaceLocator # > > Looking at general.py this seems to happen in the node creation when the > newly created Maya node can't be correctly found or is not of the correct > type. > I'm not sure what is the reason behind this error, but, considering that > it only happens when I try to instantiate this particular class ( the > product of which works perfectly if created in any other way ), I'm > thinking this may actually be a bug. > > Does anyone know what exactly may be the reason behind this behavior? Am I > doing something wrong and this is to be expected ? -- You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group. To unsubscribe from this group and stop receiving emails from it, send an email to python_inside_maya+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/47b08964-2700-4b3f-aee7-d72f44e9d042%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
