[Python-Dev] Scope, not context? (was Re: PEP 550 v3 naming) (original) (raw)
Eric Snow ericsnowcurrently at gmail.com
Thu Aug 24 12:55:05 EDT 2017
- Previous message (by thread): [Python-Dev] Scope, not context? (was Re: PEP 550 v3 naming)
- Next message (by thread): [Python-Dev] Scope, not context? (was Re: PEP 550 v3 naming)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, Aug 24, 2017 at 8:23 AM, Yury Selivanov <yselivanov.ml at gmail.com> wrote:
Contrary to scoping, the programmer is much less likely to deal with Execution Context. How often do we use "threading.local()"?
This is an important point. PEP 550 is targeting library authors, right? Most folks will not be interacting with the new functionality except perhaps indirectly via context managers. So I'm not convinced that naming collisions with more commonly used concepts is as much a concern, particularly because of conceptual similarity. However, if the functionality of the PEP would be used more commonly then the naming would be a stronger concern.
-eric
- Previous message (by thread): [Python-Dev] Scope, not context? (was Re: PEP 550 v3 naming)
- Next message (by thread): [Python-Dev] Scope, not context? (was Re: PEP 550 v3 naming)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]