Neil Schemenauer  writes:

> Even if module "a" gets reloaded, class B will continue using the old
> class A object.  There are lots of other ways this can bite.  Fixing it
> properly would be very difficult.  A 90% solution probably wouldn't be
> too hard.

http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/160164

Won't be able to make that play nice with inheritance until 2.3, but
otherwise I like it.

I don't actually *use* it, mind.  I am developing a package which I
need to reload frequently[1], but I just have a "util.reload_em()"
function which reloads everything in the right order.  That + a couple
of other details means things hardly ever get confused.

Cheers,
M.

[1] From the interactive interpreter, not a application server.

--
  It's relatively seldom that desire for sex is involved in
  technology procurement decisions.          -- ESR at EuroPython 2002