On Thu, Aug 17, 2017 at 01:03:21AM +1000, Nick Coghlan wrote: > For "ContextItem" for example, we may actually be better off calling > it "ContextKey", and have the methods be "ck.get_value()" and > "ck.set_value()". That would get us closer to the POSIX TSS > terminology, and emphasises that the objects themselves are best seen > as opaque references to a key that lets you get and set the > corresponding value in the active execution context.
+1 for "key". One is using a key to look up an item. > Avoiding a naming collision with decimal.localcontext() would also be > desirable. > > Yury, what do you think about moving the ExecutionContext name to what > the PEP currently calls LocalContext, and renaming the current > ExecutionContext type to ExecutionContextChain? For me this is already a lot clearer. Otherwise I'd call it ExecutionEnvironment. Stefan Krah _______________________________________________ Python-ideas mailing list [email protected] https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
