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 pablogsal
Recipients pablogsal
Date 2020-08-18.03:28:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1597721288.36.0.414261501326.issue41571@roundup.psfhosted.org>
In-reply-to
Content
Another possibility would be accept the reality of the switching delay (so all the other commands work without extra changes) and working to minimize it by setting sys.setswitchinterval() to something ridiculously low and then switching it back to the previous value once we are in the thread that we want. If this is not enough we could sed modify the Gil-adquire code to do something similar to what the Python 2 implementation did when signals arrive that is basically switch constantly between threads until the one that we want runs.
History
Date User Action Args
2020-08-18 03:28:08pablogsalsetrecipients: + pablogsal
2020-08-18 03:28:08pablogsalsetmessageid: <1597721288.36.0.414261501326.issue41571@roundup.psfhosted.org>
2020-08-18 03:28:08pablogsallinkissue41571 messages
2020-08-18 03:28:08pablogsalcreate