[Python-Dev] Consolidate stateful runtime globals
Benjamin Peterson
benjamin at python.org
Wed Sep 6 12:42:29 EDT 2017
More information about the Python-Dev mailing list
Wed Sep 6 12:42:29 EDT 2017
- Previous message (by thread): [Python-Dev] Consolidate stateful runtime globals
- Next message (by thread): [Python-Dev] Consolidate stateful runtime globals
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, Sep 6, 2017, at 03:14, Antoine Pitrou wrote: > > Hello, > > I'm a bit concerned about > https://github.com/python/cpython/commit/76d5abc8684bac4f2fc7cccfe2cd940923357351 > > My main gripe is that makes writing C code more tedious. Simple C > global variables such as "_once_registry" are now spelled > "_PyRuntime.warnings.once_registry". The most egregious example seems > to be "_PyRuntime.ceval.gil.locked" (used to be simply "gil_locked"). > > Granted, C is more verbose than Python, but it doesn't have to become > that verbose. I don't know about you, but when code becomes annoying > to type, I tend to try and take shortcuts. How often are you actually typing the names of runtime globals, though? If you are using a globals, perhaps the typing time will allow you to fully consider the gravity of the situation.
- Previous message (by thread): [Python-Dev] Consolidate stateful runtime globals
- Next message (by thread): [Python-Dev] Consolidate stateful runtime globals
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list