GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||||||||||||||||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||||||||||||||||||||||||||||||||
GeezerVison is showing github.com — bpo-45953: Statically allocate the main interpreter (and initial thread state). by ericsnowcurrently · Pull Request #29883 · python/cpython Conversation
|
| int | ||
| _PyEval_InitState(struct _ceval_state *ceval) | ||
| void | ||
| _PyEval_InitState(struct _ceval_state *ceval, PyThread_type_lock pending_lock) |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Would this be a good opportunity to remove this function?
The _pending_calls struct belongs on the interpreter state, not on the ceval as only the main interpreter can handle them.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
There's enough going on in this PR that I'd rather not.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
A couple of tests have been inverted.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
When you're done making the requested changes, leave the comment: |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
| } _preallocated; | ||
| }; | ||
|
|
||
| #define _PyInterpreterState_INIT \ |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
This is only used once, please remove it.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
FYI, I brought this back to avoid so much nesting and clutter in _PyRuntimeState_INIT.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
| } _preallocated; | ||
| } _PyRuntimeState; | ||
|
|
||
| #define _PyRuntimeState_INIT \ |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Might as well remove this as well. It is also only used once.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Should _Py_global_objects_INIT also move? It's pretty big and likely to get much bigger.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Actually, _PyRuntimeState_INIT is used twice.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
With basically all feedback addressed I plan on merging this soon, to unblock other changes I have waiting. If I missed something, I'd be glad to address it in a follow-up PR. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Fine with me.
…On Wed, Jan 12, 2022 at 2:56 PM Eric Snow ***@***.***> wrote:
With basically all feedback addressed I plan on merging this soon, to
unblock other changes I have waiting. If I missed something, I'd be glad to
address it in a follow-up PR.
—
Reply to this email directly, view it on GitHub
<#29883 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAWCWMXNEYDUC6YIRLTJAEDUVYBIXANCNFSM5JFJMYAA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
--
--Guido van Rossum (python.org/~guido)
|
Sorry, something went wrong.
There was an error while loading. Please reload this page.
As of CPython 3.11 (via python/cpython#29883) stdbool.h is now included in Python.h so do attempt to redefine bool/true/false.
As of CPython 3.11 (via python/cpython#29883) stdbool.h is now included in Python.h so do attempt to redefine bool/true/false.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.