On Sat, 2002-10-26 at 12:45, Edmund Lian wrote: > > Is there a way to resolve this problem automatically, or will I have to > > register a shutdownhandler to explicitly delete the global pool instance? > > Just as a follow up, I did try to register a clean up function with atexit, > but this doesn't work. And, since the module isn't a part of any context, I > don't see how I'd import and use Application.addShutdownHandler.
I suppose the problem is that you can't get to the Application object? That's annoying that it's not available -- while it's vaguely possible that you'd have two Application instances in the same process, I can't even think of a reason we'd want to keep that option open. So a reasonable fix for this problem would be to add some access to Application. I wonder if all open file objects are kept open, though? That might be a problem... I mean, not everything has to be perfect with auto-reload, since it's still only meant for development purposes. What we really want is for the Python interpreter to do a clean exit, calling all finalizers, and then restart. I don't know if you can do that with os.exec. Maybe we should ask comp.lang.python -- I'm sure we could get a definitive answer from someone. Ian ------------------------------------------------------- This SF.net email is sponsored by: ApacheCon, November 18-21 in Las Vegas (supported by COMDEX), the only Apache event to be fully supported by the ASF. http://www.apachecon.com _______________________________________________ Webware-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-devel