Merge branch 'main' into document-bytecode-specialization

Author: shreyash-bhosale

core-team/core-team.csv

@@ -1,3 +1,4 @@
+Malcolm Smith,mhsmith,2026-10-29,,
 Sergey Miryanov,sergey-miryanov,2026-10-08,,
 Nathan Goldbaum,ngoldbaum,2026-09-01,,
 Pieter Eendebak,eendebakpt,2026-07-08,,

core-team/join-team.rst

@@ -86,6 +86,10 @@ are granted through these steps:
      (Some of these are unofficial spaces managed as a courtesy.
      Adjust the list to taste.)
 
+   - If the candidate has unclaimed mannequin comments from the BPO to GitHub
+     migration, send an invite to reclaim them from
+     `🔒 Import/Export settings <https://github.com/organizations/python/settings/import-export>`__.
+     (See :ref:`what-on-earth-is-a-mannequin` for more info.)
    - Add their details to `🔒 python/voters <https://github.com/python/voters>`__.
    - Once the python/voters update is merged, regenerate the public team membership
      list at :ref:`developers`.

development-tools/clinic/howto.rst

@@ -875,6 +875,19 @@ Just name them ``__new__`` or ``__init__`` as appropriate.  Notes:
   (If your function doesn't support keywords, the parsing function
   generated will throw an exception if it receives any.)
 
+* :ref:`vectorcall protocol <python:vectorcall>` support can be added using the
+  ``@vectorcall`` directive. This will output an additional function that can be
+  used in the :c:member:`~PyTypeObject.tp_vectorcall` slot.
+  The generated function adds a fair amount of code, so benchmark first
+  and only use it where it gives a significant speedup.
+
+  Current restrictions:
+
+  * Optional groups are not supported.
+  * The type must be immutable (:c:macro:`Py_TPFLAGS_IMMUTABLETYPE`).
+
+  .. versionadded:: 3.16
+
 
 How to change and redirect Clinic's output
 ------------------------------------------

getting-started/ai-tools.rst

@@ -62,3 +62,18 @@ disrespectful of the maintainers time.
 It is not acceptable to alter or bypass existing tests, or remove desired
 functionality, in order to make a failing test pass. Such changes are not
 a real fix.
+
+How these guidelines are applied
+================================
+
+Using AI tools is not a reason on its own for an issue or PR to be labeled
+or closed. When a maintainer thinks an issue or PR does not follow these
+guidelines, they may apply one of the following labels. A bot then posts a
+comment that links to this page.
+
+- :gh-label:`AI-needs-explanation`: the issue or PR stays open. Reply in your
+  own words: explain what the change does or what the issue is about, and
+  describe how you checked that it is correct.
+- :gh-label:`AI-guidelines-not-met`: the issue or PR is closed. If you think
+  we misunderstood your contribution, reply on the issue or PR. You are
+  welcome to explain your approach or ask questions about these guidelines.

getting-started/setup-building.rst

@@ -781,8 +781,8 @@ some of CPython's modules (for example, ``zlib``).
          $ sudo dnf install \
                gcc gcc-c++ gdb lzma glibc-devel libstdc++-devel openssl-devel \
                readline-devel zlib-devel libzstd-devel libffi-devel bzip2-devel \
-               xz-devel sqlite sqlite-devel sqlite-libs libuuid-devel gdbm-libs \
-               perf expat expat-devel mpdecimal python3-pip
+               xz-devel sqlite sqlite-devel sqlite-libs libuuid-devel gdbm-devel \
+               perf expat expat-devel mpdecimal-devel tk-devel python3-pip
 
    .. tab:: Debian / Ubuntu
 

testing/run-write-tests.rst

@@ -17,29 +17,29 @@ Running and writing tests
 Running
 =======
 
-The shortest, simplest way of running the test suite is the following command
-from the root directory of your checkout (after you have
-:ref:`built Python <compiling>`):
+The shortest, simplest way of running the test suite is the following command,
+which runs tests in parallel, from the root directory of your checkout
+(after you have :ref:`built Python <compiling>`):
 
 .. tab:: Unix
 
     .. code-block:: shell
 
-        ./python -m test
+        ./python -m test -j0
 
 .. tab:: macOS
 
     .. code-block:: shell
 
-        ./python.exe -m test
+        ./python.exe -m test -j0
 
     This works on :ref:`most <mac-python.exe>` macOS systems.
 
 .. tab:: Windows
 
     .. code-block:: dosbatch
 
-        .\python.bat -m test
+        .\python.bat -m test -j0
 
 This will run the majority of tests, but exclude a small portion of them; these
 excluded tests use special kinds of resources: for example, accessing the
@@ -139,26 +139,31 @@ But, there are several important notes:
    In other words: if some module does not have ``unittest.main()``, then
    most likely it does not support direct invocation.
 
-If you have a multi-core or multi-CPU machine, you can enable parallel testing
-using several Python processes so as to speed up things:
+By default, ``-j0`` runs tests in parallel using a number of worker processes
+based on the CPU count, which is much faster but can interleave output
+from different tests. To run tests sequentially, for example when debugging
+a failure, drop the ``-j`` flag:
 
 .. tab:: Unix
 
     .. code-block:: shell
 
-        ./python -m test -j0
+        ./python -m test
 
 .. tab:: macOS
 
     .. code-block:: shell
 
-        ./python.exe -m test -j0
+        ./python.exe -m test
 
 .. tab:: Windows
 
     .. code-block:: dosbatch
 
-        .\python.bat -m test -j0
+        .\python.bat -m test
+
+To limit how many tests run at once, pass an explicit number of
+worker processes instead, such as ``-j2``.
 
 .. _strenuous_testing:
 

triage/issue-tracker.rst

@@ -201,6 +201,11 @@ that happened in the issue. In case the user did share their GitHub account
 name in their BPO profile, we use that. Otherwise, their classic BPO
 username is used instead.
 
+For triagers and core team members, :ref:`organization owners <current owners>`
+can send invitations to attribute mannequin comments to GitHub user account.
+(For the administrator: use the `Import/Export settings page <mannequin-reclaim-settings_>`_;
+refer to `Github's documentation <mannequin-reclaim-docs_>`_.)
+
 
 .. _disagreement-with-a-resolution-on-the-issue-tracker:
 
@@ -239,3 +244,5 @@ reason either as ``complete`` or ``not planned``.
 .. _sub-issues: https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/adding-sub-issues
 .. _Core Development Discourse category: https://discuss.python.org/c/core-dev/23
 .. _old bug tracker: https://bugs.python.org/
+.. _mannequin-reclaim-settings: https://github.com/organizations/python/settings/import-export
+.. _mannequin-reclaim-docs: https://docs.github.com/en/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/reclaiming-mannequins-for-github-enterprise-importer#reclaiming-mannequins-in-your-browser

triage/labels.rst

@@ -116,6 +116,16 @@ for a list of active branches.
 Other labels
 ============
 
+* Use :gh-label:`AI-guidelines-not-met` for a clearly low-effort
+  AI-assisted submission where you think the author is unlikely to engage with
+  feedback. The bot links to the :ref:`guidelines for using AI tools
+  <ai-tools>` and closes the issue or PR. See the :ref:`triage team's guidance
+  on applying the AI policy labels <triage-ai-labels>`.
+* Use :gh-label:`AI-needs-explanation` when you have concerns
+  about AI-assisted work and think the author is likely to engage with feedback.
+  The bot posts a reminder and leaves the issue or PR open. See the
+  :ref:`triage team's guidance on applying the AI policy labels
+  <triage-ai-labels>`.
 * :gh-label:`build`/:gh-label:`performance`: for issues related
   to the build process or performance, respectively.
 * :gh-label:`easy`: for issues that are considered easy.

triage/triage-team.rst

@@ -56,6 +56,39 @@ the Python Software Foundation, always follow the `PSF Code of Conduct`_.
 .. _PSF Code of Conduct: https://policies.python.org/python.org/code-of-conduct/
 
 
+.. _triage-ai-labels:
+
+Applying the AI policy labels
+=============================
+
+Use the AI policy labels for issues and PRs that don't follow the
+:ref:`guidelines for using AI tools <ai-tools>`. Don't apply them only because
+AI tools were used, or because the author disclosed using them.
+
+Apply only one of these labels to an issue or PR. When you add
+:gh-label:`AI-guidelines-not-met`, the bot automatically removes
+:gh-label:`AI-needs-explanation`. If you add both labels,
+:gh-label:`AI-guidelines-not-met` wins.
+
+* Start with :gh-label:`AI-needs-explanation`. The bot asks the author to
+  explain the work in their own words and leaves the issue or PR open.
+* Use :gh-label:`AI-guidelines-not-met` only for clear cases, such as a
+  low-effort submission where the author is unlikely to engage with feedback.
+  The bot posts a comment and closes the issue or PR. If you have any doubt,
+  use :gh-label:`AI-needs-explanation` instead, or consult a core developer.
+* If the author doesn't respond to :gh-label:`AI-needs-explanation`, or the
+  response doesn't address the concern (for example, it is more generated
+  text), add :gh-label:`AI-guidelines-not-met`. The bot removes
+  :gh-label:`AI-needs-explanation`, posts the closing comment and closes the
+  issue or PR. If you have any doubt, consult a core team member first.
+* If the author responds and the concern is resolved, remove the label.
+  For a closed issue or PR, reopen it as well.
+
+Prefer these labels over closing manually, so the author gets the same
+explanation each time and the issues and PRs can be found later by filtering
+on the label.
+
+
 Becoming a member of the Python triage team
 ===========================================
 

triage/triaging.rst

@@ -28,6 +28,8 @@ Checklist for triaging
 * If the issue is clearly invalid (unrelated to CPython, spam, and
   so on), you can use GitHub's :guilabel:`Close as not planned` option
   and apply the :gh-label:`invalid` label.
+* If the issue or PR doesn't follow the :ref:`guidelines for using AI tools
+  <ai-tools>`, apply one of the :ref:`AI policy labels <triage-ai-labels>`.
 
 
 .. _triage-fields: