➜
See More

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eric.snow
Recipients eric.snow
Date 2021-12-07.20:24:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <[email protected]>
In-reply-to
Content 
There are a few things in `_PyRuntimeState`, `PyInterpreterState`, `PyThreadState`, and there initialization (Python/pystate.c & Python/pylifecycle.c) that would benefit from some minor cleanup.  Normally I wouldn't bother (due to the cost of churn), but such cleanup would help with other changes I'm working on.

The cleanup includes:

* move thread related interpreter state to `PyInterpreterState.threads`
* return void from `_PyEval_InitState()`
* separate Py*State initialization from creation
* distinguish between initialized-to-safe-state and ready-to-use
* separate init for global types/objects into phases: object state vs. global objects vs. global types
History
Date User Action Args
2021-12-07 20:24:26eric.snowsetrecipients: + eric.snow
2021-12-07 20:24:26eric.snowsetmessageid: <[email protected]>
2021-12-07 20:24:26eric.snowlinkissue46008 messages
2021-12-07 20:24:26eric.snowcreate