News for hackers. Stuff that matters.
Re:Data races in Python, despite the Global Interpreter Lock by verdagon on Monday February 21, 2022 @05:15PM (#30421375)
Author here, u/skeeto from https://www.reddit.com/r/programming/comments/sxy5q4/pythons... has some good insight into the 3.10 difference:

> Ironically, CPython 3.10 has gone the opposite direction and made thread scheduling much more deterministic. It now only releases the GIL on backwards edges in the byte code The example in the article always prints 40000000 in CPython 3.10! I expect this will ultimately make Python code less reliable in the future as many programs will accidentally depend on this behavior.

Re:Data races in Python, despite the Global Interpreter Lock by andreareina on Monday February 21, 2022 @07:13PM (#30422506)
Does this mean loops/function call/return?
Re:Data races in Python, despite the Global Interpreter Lock by rwbhn on Monday February 21, 2022 @10:08PM (#30423613)
Yes. A comment in the referenced commit says "when returning from a call or on the back edges of loops."