RetroSearch Browse

Tue Aug 29 09:46:20 EDT 2017 · https://mail.python.org/pipermail/python-dev/2017-August/149048.html

On Tuesday, August 29, 2017 9:14:53 AM EDT Yury Selivanov wrote:
> On Tue, Aug 29, 2017 at 6:53 AM, Nick Coghlan <ncoghlan at gmail.com> 
wrote:
> > On 28 August 2017 at 01:51, Jim J. Jewett <jimjjewett at gmail.com> 
wrote:
> >> I think there is general consensus that this should go in a module
> >> other than sys. (At least a submodule.)
> >> 
> >> The specific names are still To Be Determined, but I suspect seeing
> >> the functions and objects as part of a named module will affect
> >> what works.> 
> > Given the refocusing of the PEP on the context variable API, with
> > the
> > other aspects introduced solely in service of making context
> > variables work as defined, my current suggestion would be to make
> > it a hybrid Python/C API using the "contextvars" + "_contextvars"
> > naming convention.
> > 
> > Then all most end user applications defining context variables would
> > 
> > need is the single line:
> >     from contextvars import new_context_var
> 
> I like it!
> 
> +1 from me.

+1

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

Showing content from https://mail.python.org/pipermail/python-dev/2017-August/149048.html below:

[Python-Dev] Pep 550 module