The way we came to "logical context" was via "logical thread (of control)", which is distinct from OS thread. But I think we might need to search for another term... On Aug 19, 2017 11:56 AM, "Ethan Furman" <ethan at stoneleaf.us> wrote: > On 08/19/2017 01:40 AM, Antoine Pitrou wrote: > >> On Fri, 18 Aug 2017 16:33:27 -0400 Yury Selivanov wrote: >> > > There are a few open questions left, namely the terminology >>> and design of ContextKey API. On the former topic, I'm quite >>> happy with the latest version: Execution Context, Logical >>> Context, and Context Key. >>> >> >> I don't really like it. "Logical Context" is vague (there are >> lots of things called "context" in other libraries, so a bit of >> specificity would help avoid confusion), and it's not clear what is >> "logical" about it anyway. "Local Context" actually seemed better to >> me (as it reminded of threading.local() or the general notion of >> thread-local storage). >> > > I am also not seeing the link between "logical" and "this local layer of > environmental changes that won't be seen by those who called me". > > Maybe ContextLayer? Or marry the two and call it LocalContextLayer. > > -- > ~Ethan~ > > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: https://mail.python.org/mailman/options/python-dev/guido% > 40python.org > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20170819/ba733444/attachment.html>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4