summaryrefslogtreecommitdiffstats
path: root/Misc/NEWS.d/next/Core and Builtins/2023-12-13-11-45-53.gh-issue-106905.5dslTN.rst
diff options
context:
space:
mode:
Diffstat (limited to 'Misc/NEWS.d/next/Core and Builtins/2023-12-13-11-45-53.gh-issue-106905.5dslTN.rst')
-rw-r--r--Misc/NEWS.d/next/Core and Builtins/2023-12-13-11-45-53.gh-issue-106905.5dslTN.rst7
1 files changed, 0 insertions, 7 deletions
diff --git a/Misc/NEWS.d/next/Core and Builtins/2023-12-13-11-45-53.gh-issue-106905.5dslTN.rst b/Misc/NEWS.d/next/Core and Builtins/2023-12-13-11-45-53.gh-issue-106905.5dslTN.rst
deleted file mode 100644
index e3a772f..0000000
--- a/Misc/NEWS.d/next/Core and Builtins/2023-12-13-11-45-53.gh-issue-106905.5dslTN.rst
+++ /dev/null
@@ -1,7 +0,0 @@
-Use per AST-parser state rather than global state to track recursion depth
-within the AST parser to prevent potential race condition due to
-simultaneous parsing.
-
-The issue primarily showed up in 3.11 by multithreaded users of
-:func:`ast.parse`. In 3.12 a change to when garbage collection can be
-triggered prevented the race condition from occurring.