[Python-Dev] Scope, not context? (was Re: PEP 550 v3 naming) (original) (raw)
Antoine Pitrou solipsis at pitrou.net
Thu Aug 24 10:02:29 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, 24 Aug 2017 09:52:47 -0400 Barry Warsaw <barry at python.org> wrote:
To me, the functionality proposed in PEP 550 feels more like a "scope" than a "context".
I would call it "environment" myself, but that risks confusion with environment variables.
Perhaps "dynamic environment" would remove the confusion.
One other suggestion: maybe we shouldn't put these new functions in sys, but instead put them in their own module? It feels analogous to the gc module; all those functions could have gone in sys since they query and effect the Python runtime system, but it makes more sense (and improves the naming) by putting them in their own module. It also segregates the functionality so that sys doesn't become a catchall that overloads you when you're reading through the sys module documentation.
+1 from me.
Regards
Antoine.
- 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 ]