RetroSearch Browse

Fri Apr 28 02:20:21 CEST 2006 · https://mail.python.org/pipermail/python-dev/2006-April/064515.html

+1 from me too.

On 4/27/06, Edward Loper <edloper at gradient.cis.upenn.edu> wrote:
> Nick Coghlan wrote:
> > OTOH, if the two protocols are made orthogonal, then it's clear that the
> > manager is always the original object with the __context__ method. Then the
> > three cases are:
> >
> >   - a pure context manager (only provides __context__)
> >   - a pure managed context (only provides __enter__/__exit__)
> >   - a managed context which can be its own context manager (provides all three)
>
> +1 on keeping the two protocols orthogonal and using this terminology
> (context manager/managed context).
>
> -Edward
> _______________________________________________
> Python-Dev mailing list
> Python-Dev at python.org
> http://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe: http://mail.python.org/mailman/options/python-dev/guido%40python.org
>


--
--Guido van Rossum (home page: http://www.python.org/~guido/)

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

Showing content from https://mail.python.org/pipermail/python-dev/2006-April/064515.html below:

[Python-Dev] Must objects with enter/exit also supply context?

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

Showing content from https://mail.python.org/pipermail/python-dev/2006-April/064515.html below:

[Python-Dev] Must objects with __enter__/__exit__ also supply __context__?

[Python-Dev] Must objects with enter/exit also supply context?