bpo-40512: Store pointer to interpreter state in a thread local variable#29228
bpo-40512: Store pointer to interpreter state in a thread local variable#29228markshannon wants to merge 11 commits into
Conversation
1be2ad9 to
ada883d
Compare
October 26, 2021 15:49
|
🤖 New build scheduled with the buildbot fleet by @markshannon for commit ada883d6b97bb072ef8465b71671ef9db101c7ae 🤖 If you want to schedule another build, you need to add the ":hammer: test-with-buildbots" label again. |
Sorry, something went wrong.
|
Build failures look like the usual suspects. |
Sorry, something went wrong.
ada883d to
f22036b
Compare
October 27, 2021 15:06
|
The old approach had a NULL check and |
Sorry, something went wrong.
Sorry, I don't have the bandwidth to review this change :-( |
Sorry, something went wrong.
|
I'm dropping this as there are a few reasons why passing the interpreter state explicitly make sense.
|
Sorry, something went wrong.
A more future proof way to handle interpreter state. 1% faster as well.
https://bugs.python.org/issue40512