tree b282c1b565d7ad97f789683dac78c2dfc767027f
parent d2a8e5b42c5e9c4e745a0589043a8aebb49f8ca2
author Victor Stinner <vstinner@python.org> 1584712235 +0100
committer GitHub <noreply@github.com> 1584712235 +0100
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJedMorCRBK7hj4Ov3rIwAAdHIIAFz5ToViKE5R+j18s74a04Xb
 G3xfC4IfSDa81T0oe0CrYL98VS+5FZw6n7mn+IIIAd9LkSmovW/RCyDeX0AsjNxb
 8AaGmR3mmKundRsLxrdZS7iIp143aQ358e7nwVIRMg9SqATCtn2pX4Ttmrq9vVr+
 qUQaeeCWXqlNSFIVrXVn7cKNfWrgdlcyvsH9S2fKhmQXNvBp19G4sfjJQwH0oAlY
 Y0Jhpsg7twLPXzYxvKuay5YwU8mhQhceO61m7c7znALz4wNSXfqxFtuRbdaDKP5X
 1J1W7yRePmDripH56KNLqOSGFdRSMePnTi91fR9dqFaZWcDIXuSXkqJjhZaVjmA=
 =uzv8
 -----END PGP SIGNATURE-----
 

bpo-40010: Optimize pending calls in multithreaded applications (GH-19091)

If a thread different than the main thread schedules a pending call
(Py_AddPendingCall()), the bytecode evaluation loop is no longer
interrupted at each bytecode instruction to check for pending calls
which cannot be executed. Only the main thread can execute pending
calls.

Previously, the bytecode evaluation loop was interrupted at each
instruction until the main thread executes pending calls.

* Add _Py_ThreadCanHandlePendingCalls() function.
* SIGNAL_PENDING_CALLS() now only sets eval_breaker to 1 if the
  current thread can execute pending calls. Only the main thread can
  execute pending calls.