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/2005-July/054665.html below:

[Python-Dev] 'With' context documentation draft (was Re: Terminology for PEP 343

[Python-Dev] 'With' context documentation draft (was Re: Terminology for PEP 343 [Python-Dev] 'With' context documentation draft (was Re: Terminology for PEP 343Reinhold Birkenfeld reinhold-birkenfeld-nospam at wolke7.net
Wed Jul 6 15:14:46 CEST 2005
Paul Moore wrote:
> On 7/6/05, Michael Chermside <mcherm at mcherm.com> wrote:
>> Paul Moore writes:
>> > I also like the fact that it offers a neat 1-word name for the
>> > generator decorator, "@context".
>> 
>> Well, ok... does anyone *else* agree? I too saw this and thought "neat!
>> a simple one-word name!". But then I started worrying that it's not
>> defining the *context*, but rather the *context manager*. While
>> "context manager" is a term I could easily imagine associating only
>> with 'with' statements, "context" is too general a term... even after
>> Python supports 'with' statements I will continue to use "context"
>> to mean lots of different things (eg: decimal.context).
> 
> Actually, you're starting to persuade me... Although I generally
> prefer decorator names which are single words. Along with the at-sign,
> underscores make the whole thing look a little too "punctuation-heavy"
> for me (and don't suggest camel case, please!).

Anything against

@contextmanager

in analogy to

@staticmethod

?

Reinhold

-- 
Mail address is perfectly valid!

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