Re: Re: loading an object's state

> This is to prevent the computation done in __setstate__ from
> causing the object to register itself as changed.  An object
> won't generate a changed event if it is already in the changed state.

This is decidedly non-trivial!  I expect Jeremy will add a comment to
this effect to the code.

--Guido van Rossum (home page: http://www.python.org/~guido/)