I'm getting that a lot lately, too, and haven't found anything useful on the interwebs either. Would love to make it go away. Right now I'm resorting to ripping out chunks of Python code to try to narrow down where it's happening.
P.S. Hi, Den :-) On Aug 28, 2015 2:38 PM, "Den Serras" <denserras...@gmail.com> wrote: > Am I the only person plagued by the "A PythonObject is not attached to a > node" error? There's very little about it on the Web considering how often > it plagues me, almost like it's following me from studio to studio... It's > not even consistent. A relaunch will make it go away. Refreshing a node > will make it appear. Sometimes. > > Argh, > Den > > _______________________________________________ > Nuke-python mailing list > Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python > >
_______________________________________________ Nuke-python mailing list Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
