"Ron Garret" <[EMAIL PROTECTED]> wrote:
> > One of the things I find annoying about Python is that when you make a > change to a method definition that change is not reflected in existing > instances of a class (because you're really defining a new class when > you reload a class definition, not actually redefining it). So I came > up with this programming style: I would have thought that not changing yesterday was the very essence of dynamism (dynamicness ??) - but that when you change something - it applies from that point in time forwards... What do you propose to do about the outputs from such classes that have already happened? confused - Hendrik -- http://mail.python.org/mailman/listinfo/python-list
