> It's a well known bug. There is in fact no leak. Cool, good to know.
> So you could keep a list containing all of your callback ids, creating > a new list entry for each one. That would eliminate the warning > message while, perversely, creating a *real* memory leak. But at least > the leak would be under your control. Heh... if there's no leak, and it's just a stray warning message, I think I'd probably rather just NOT assign it to a variable, and (temporarily) redirect stdout/stderr. Thanks for the info though... it's comforting to know I can just safely ignore it. =) - Paul --~--~---------~--~----~------------~-------~--~----~ Yours, Maya-Python Club Team. -~----------~----~----~----~------~----~------~--~---
