On Tue, Aug 29, 2017 at 6:46 AM, Elvis Pranskevichus <elpr...@gmail.com>
wrote:
> On Tuesday, August 29, 2017 9:14:53 AM EDT Yury Selivanov wrote:
> > On Tue, Aug 29, 2017 at 6:53 AM, Nick Coghlan <ncogh...@gmail.com>
> wrote:
> > > 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
>
OK, but does it have to look like a factory function? Can't it look like a
class? E.g.
from contextvars import ContextVar
my_parameter = ContextVar()
async def some_calculation():
my_parameter.set(my_parameter.get() + 2)
<DO STUFF>
my_parameter.delete()
--
--Guido van Rossum (python.org/~guido <http://python.org/%7Eguido>)
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
