Restated, instead of a common or mutex lock, they are now going to use a per interpreter instance lock. A long time overdue, but the author’s assertion of “truly concurrent Python code” is incorrect and should have been stated otherwise. The real implication is that when multiple Python interpreters are in use within a single process, the interpreters are no longer single threaded by the use of a common GIL (Global Interpreter Lock). In other words, they’re fixing an issue that most Python programmers don’t use directly, but is a feature used by major library routines (for example, AI). The author finally makes this admission directly in their conclusion.
Mark L. Gaubatz From: Jean Louis Faucher Sent: Tuesday, May 16, 2023 07:37 To: Open Object Rexx Developer Mailing List <oorexx-devel@lists.sourceforge.net> Subject: [Oorexx-devel] "Per-Interpreter GIL" will land in Python 3.12 I saw this link in the daily TLDR mail of today: https://martinheinz.dev/blog/97 Real Multithreading is Coming to Python - Learn How You Can Use It Now Did not read in details yet, but seems worth to understand how they implemented their "Per-Interpreter GIL”.
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
