[Python-ideas] PEP draft: context variables
Koos Zevenhoven
k7hoven at gmail.com
Tue Sep 5 13:53:33 EDT 2017
More information about the Python-ideas mailing list
Tue Sep 5 13:53:33 EDT 2017
- Previous message (by thread): [Python-ideas] PEP draft: context variables
- Next message (by thread): [Python-ideas] PEP draft: context variables
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, Sep 5, 2017 at 8:43 PM, Yury Selivanov <yselivanov.ml at gmail.com> wrote: > On Tue, Sep 5, 2017 at 10:31 AM, Koos Zevenhoven <k7hoven at gmail.com> > wrote: > > On Tue, Sep 5, 2017 at 8:24 PM, Yury Selivanov <yselivanov.ml at gmail.com> > > wrote: > >> > >> I don't actually care if you use the latest terminology. You seem to > >> have a wrong idea about how PEP 550 really works (and its full > >> semantics), because things you say here about it don't make any sense. > > > > > > In PEP 550, introducing a new LogicalContext on the ExecutionContext > affects > > the scope of > > any_var.set(value) for *any* any_var. > > Does that not make sense? > > It does. But your other sentence ".. You might get close by putting > just one variable in a LogicalContext and then nest them, but PEP 550 > does not allow this in all cases .." does not. > So you claim that PEP 550 does allow that in all cases? Or you don't think that that would get close? ––Koos -- + Koos Zevenhoven + http://twitter.com/k7hoven + -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-ideas/attachments/20170905/d5029c0b/attachment.html>
- Previous message (by thread): [Python-ideas] PEP draft: context variables
- Next message (by thread): [Python-ideas] PEP draft: context variables
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-ideas mailing list