Hi Viktoras, You're correct; this has nothing to do with Qt in particular, I was just referencing that discussion because it had a starting point for the code.
My procedure is doing the same unregistration as yours, so mostly I think we're on the same track. I'm doing two additional things to make debugging in the Script Editor handy: - If the module is also registered to a global (because I previously did something like "import MyModule" in the Script Editor), delete the global. - Always re-import the top-level module, so that future Script Editor debugging can proceed from that point. But in general, yeah, I'm counting on the code to have the correct import statements to pull all the sub-modules back in as they are invoked. Leo On Jun 7, 11:22 pm, Viktoras <[email protected]> wrote: > is it PyQT related problem, or are you looking at a simple problem of > reimporting python modules after editing them? for later, we just use a > "unload" mechanic. that is, we're not hotswapping new versions of > modules, resolving dependencies would be too hard; we're unloading every > single bit of code so that it's read from disc next time it's loaded. > this is provided your whole code is packaged: -- http://groups.google.com/group/python_inside_maya
