"[EMAIL PROTECTED]" wrote:
> After all, the fact that Python is not strongly typed and is
> interpreted rather than compiled
if you think those are facts, you don't understand how Python
works.
(hint: Python's both strongly typed *and* compiled)
> sacrificing programmer producitivity
the abili
[EMAIL PROTECTED] wrote:
>
> But I am still puzzled by the argument that has been given for why
> methods that operate on mutable types should return None, namely, that
> the designers of python didn't want the users to shoot themselves in
> the foot by thinking a method simply returned a result an
In a previous post, I asked about the inconsistency in usage patterns
in operating on mutable and immutable types. Thanks Dave and everyone
else for answering my question so thoughtfully and helping me to
understand the reasoning about why the different usage patterns are not
deemed to be inconsist
