PEP 684: Minor Updates (python#3004)

ericsnowcurrently · web-flow · commit bb5033050741 · 2023-02-03T15:49:21.000-07:00
I had forgotten to update the Post-History header back in October. There was also one minor point from that round of discussion that I had not added to the PEP yet.
diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml
@@ -223,7 +223,7 @@ repos:
       - id: validate-post-history
         name: "'Post-History' must be '`DD-mmm-YYYY <Thread URL>`__, ...'"
         language: pygrep
-        entry: '(?<=\n)Post-History:(?:(?! ?\n|((( +|\n {1,14})(([0-2][0-9]|(3[01]))-(Jan|Feb|Mar|Apr|May|Jun|Jul|Aug|Sep|Oct|Nov|Dec)-(199[0-9]|20[0-9][0-9])|`([0-2][0-9]|(3[01]))-(Jan|Feb|Mar|Apr|May|Jun|Jul|Aug|Sep|Oct|Nov|Dec)-(199[0-9]|20[0-9][0-9]) <https://((discuss\.python\.org/t/([\w\-]+/)?\d+/?)|(mail\.python\.org/pipermail/[\w\-]+/\d{4}-[A-Za-z]+/[A-Za-z0-9]+\.html)|(mail\.python\.org/archives/list/[\w\-]+@python\.org/thread/[A-Za-z0-9]+/?(#[A-Za-z0-9]+)?))>`__)(,|(?=\n[^ ])))+\n(?=[A-Z\n]))))'
+        entry: '(?<=\n)Post-History:(?:(?! ?\n|((( +|\n {1,14})(([0-2][0-9]|(3[01]))-(Jan|Feb|Mar|Apr|May|Jun|Jul|Aug|Sep|Oct|Nov|Dec)-(199[0-9]|20[0-9][0-9])|`([0-2][0-9]|(3[01]))-(Jan|Feb|Mar|Apr|May|Jun|Jul|Aug|Sep|Oct|Nov|Dec)-(199[0-9]|20[0-9][0-9]) <https://((discuss\.python\.org/t/([\w\-]+/)?\d+(?:/\d+)?/?)|(mail\.python\.org/pipermail/[\w\-]+/\d{4}-[A-Za-z]+/[A-Za-z0-9]+\.html)|(mail\.python\.org/archives/list/[\w\-]+@python\.org/thread/[A-Za-z0-9]+/?(#[A-Za-z0-9]+)?))>`__)(,|(?=\n[^ ])))+\n(?=[A-Z\n]))))'
         args: [--multiline]
         files: '^pep-\d+\.(rst|txt)$'
         types: [text]
diff --git a/pep-0684.rst b/pep-0684.rst
@@ -10,6 +10,7 @@ Created: 08-Mar-2022
 Python-Version: 3.12
 Post-History: `08-Mar-2022 <https://mail.python.org/archives/list/python-dev@python.org/thread/CF7B7FMACFYDAHU6NPBEVEY6TOSGICXU/>`__,
               `29-Sep-2022 <https://discuss.python.org/t/pep-684-a-per-interpreter-gil/19583>`__,
+              `28-Oct-2022 <https://discuss.python.org/t/pep-684-a-per-interpreter-gil/19583/19>`__,
 Resolution:
 
 
@@ -401,6 +402,10 @@ on the GIL for thread safety.
 In ``PyInterpreterConfig_INIT``, this will be ``true``.
 In ``PyInterpreterConfig_LEGACY_INIT``, this will be ``false``.
 
+Also, to play it safe, for now we will not allow ``own_gil`` to be true
+if a custom allocator was set during runtime init.  Wrapping the allocator,
+a la tracemalloc, will still be fine.
+
 PyInterpreterConfig.strict_extensions_compat
 ''''''''''''''''''''''''''''''''''''''''''''
 
