Re: Why require __init__ to return None?
Mon, 30 May 1994 09:49:37 +0200

> To followup my own post (again)... it might be useful to be able to
> change the __call__ method (perhaps to simulate coroutines if you
> don't have threads). Unfortunately, giving it the name __call__ makes
> it a read-only property.

That's a non-problem, since the user defines __call__ in the first
place. If you plan for an extension you can define your __call__ to
call '_call_' if you want; to change an existing class you can alway
derive a new class and and give it a different __call__ method...

--Guido van Rossum, CWI, Amsterdam <>
URL: <>