RetroSearch Browse

Fri Jul 17 08:30:51 CEST 2015 · https://mail.python.org/pipermail/python-dev/2015-July/140790.html

On 17 July 2015 at 08:30, Ben Finney <ben+python at benfinney.id.au> wrote:
> By definition, advocating to not add cruft to an API is going to be in
> advance of being bitten by those additions.

That's not what people are doing. Folks are actually arguing for
*restoring* the ability to mock out method names starting with
"assret_*".

I still don't know why anyone thinks restoring that would be a
worthwhile use of a maintainers' time (or why they thinking arguing in
favour of such a capability is a worthwhile use of theirs).

None of the perspectives presented in this thread are new, although
the apparent obsession over such a minor detail has made it abundantly
clear that this kind of helper simply isn't worth the distraction it
creates for maintainers, *regardless* of whether or not it helps end
users.

Regards,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2015-July/140790.html below:

[Python-Dev] How far to go with user-friendliness