[Python-Dev] Pep 550 module (original) (raw)
Elvis Pranskevichus elprans at gmail.com
Tue Aug 29 09:46:20 EDT 2017
- Previous message (by thread): [Python-Dev] Pep 550 module
- Next message (by thread): [Python-Dev] Pep 550 module
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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 newcontextvar
I like it! +1 from me.
+1
- Previous message (by thread): [Python-Dev] Pep 550 module
- Next message (by thread): [Python-Dev] Pep 550 module
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]