On Mon, Oct 1, 2012 at 12:35 AM, Chris Angelico <ros...@gmail.com> wrote: > What I'm talking about is > having a single process that never terminates, never stops accepting > connections, but at some point new connections begin to be served with > new code...
And to clarify, only the code that needs updating gets updated; in-memory state is retained elsewhere, and modules are permitted and welcome to use a "global state area" that doesn't get wiped on any code reload. ChrisA -- http://mail.python.org/mailman/listinfo/python-list
