A RetroSearch Logo

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

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2013-October/129793.html below:

[Python-Dev] Coding practice for context managers

[Python-Dev] Coding practice for context managers [Python-Dev] Coding practice for context managersPaul Moore p.f.moore at gmail.com
Mon Oct 21 13:11:57 CEST 2013
On 21 October 2013 11:59, R. David Murray <rdmurray at bitdance.com> wrote:
> On Sun, 20 Oct 2013 19:49:24 -0700, Ethan Furman <ethan at stoneleaf.us> wrote:
>> On 10/20/2013 07:42 PM, Raymond Hettinger wrote:
>> >
>> > In short, I recommend that efforts be directed at improving help() rather than limiting introspection by way of less clean coding practices.
>>
>> +1
>
> I'm also +1 on improving help instead of using wrapper classes.

Agreed. A wrapper function whose purpose is solely to tidy up help
seems like a bad idea in general.

I'm somewhat more sympathetic to Nick's point that the name the user
types should be all-lowercase and a class would be mixed case, but on
that I think it's actually the naming convention that should change
(name classes/functions based on usage, not implementation). The rule
to me is that changing the underlying implementation shouldn't affect
the user interface.

Paul
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4