Uniform Function Call Syntax (UFCS)

[jongiddy]

On Sunday, 8 June 2014 02:27:42 UTC+1, Gregory Ewing  wrote:
> 
> Also it doesn't sit well with Python's "one obvious
> way to do it" guideline, because it means there are
> *two* equally obvious ways to call a function.

Actually, one of the best arguments against introducing UFCS is that Python currently provides two equivalent ways to check if an instance has an attribute: ask-permission using hasattr and ask-forgiveness using AttributeError.

On the negative side, these currently equivalent (aside from performance) techniques could give different results using UFCS, potentially breaking some code.

On the positive side, that means the proposal would add one "two ways to do something" and eliminate another "two ways to do something", giving a net Zen of Python effect of zero.