Python is DOOMED! Again!

[Jon Ribbens]

On 2015-01-22, Steven D'Aprano <steve+comp.lang.python at pearwood.info> wrote:
> You can't use "raise" as a parameter name, since that's a keyword. Using
> floats for money is Just Wrong and anyone who does so should have their
> licence to program taken away. And I really don't understand what this
> function is supposed to do, that it returns None, a single Employee, or a
> sequence of Employees. (If it's hard to declare what the return type is,
> perhaps your function does too much or the wrong thing.)

That makes me think - it seems odd to me that PEP 484 doesn't even
mention function overloading (even to say that it's outside the
scope).

I think overloading should certainly be considered, and unless the
consensus is that it is something that should never happen, it
should either be explicitly allowed or at least the type-hinting
syntax should be checked to ensure it is forward-compatible with it.