Merge branch 'main' into file_upload_mechanisms

Author: ewdurbin

.github/CODEOWNERS

@@ -673,7 +673,9 @@ peps/pep-0791.rst  @vstinner
 peps/pep-0792.rst  @dstufft
 peps/pep-0793.rst  @encukou
 peps/pep-0794.rst  @brettcannon
-# ...
+peps/pep-0798.rst  @JelleZijlstra
+peps/pep-0799.rst  @pablogsal
+peps/pep-0800.rst  @JelleZijlstra
 peps/pep-0801.rst  @warsaw
 # ...
 peps/pep-2026.rst  @hugovk

Makefile

@@ -64,6 +64,7 @@ venv:
 		echo "venv already exists."; \
 		echo "To recreate it, remove it first with \`make clean-venv'."; \
 	else \
+		set -e; \
 		echo "Creating venv in $(VENVDIR)"; \
 		if $(UV) --version >/dev/null 2>&1; then \
 			$(UV) venv --python=$(PYTHON) $(VENVDIR); \

peps/pep-0011.rst

@@ -102,7 +102,7 @@ Tier 2
 Target Triple                 Notes                      Contacts
 ============================= ========================== ========
 aarch64-unknown-linux-gnu     glibc, clang               Victor Stinner, Gregory P. Smith
-wasm32-unknown-wasip1         WASI SDK, Wasmtime         Brett Cannon, Eric Snow
+wasm32-unknown-wasip1         WASI SDK, Wasmtime         Brett Cannon, Michael Droettboom
 x86_64-unknown-linux-gnu      glibc, clang               Victor Stinner, Gregory P. Smith
 ============================= ========================== ========
 

peps/pep-0590.rst

@@ -2,7 +2,7 @@ PEP: 590
 Title: Vectorcall: a fast calling protocol for CPython
 Author: Mark Shannon <mark@hotpy.org>, Jeroen Demeyer <J.Demeyer@UGent.be>
 BDFL-Delegate: Petr Viktorin <encukou@gmail.com>
-Status: Accepted
+Status: Final
 Type: Standards Track
 Created: 29-Mar-2019
 Python-Version: 3.8

peps/pep-0628.rst

@@ -30,7 +30,7 @@ The idea in this PEP has been implemented in the auspiciously named
 `issue 12345`_.
 
 .. _accepted: https://bugs.python.org/issue12345#msg272287
-.. _issue 12345: http://bugs.python.org/issue12345
+.. _issue 12345: https://bugs.python.org/issue12345
 
 
 The Rationale for Tau
@@ -65,12 +65,12 @@ may be of interest:
   highlighting the problems with ``pi`` has `a page of resources`_ on the
   topic
 * For those that prefer videos to written text, `Pi is wrong!`_ and
-  `Pi is (still) wrong`_ are available on YouTube
+  `Pi is (still) wrong`_ are available.
 
-.. _Tau Manifesto: http://tauday.com/
-.. _Pi is (still) wrong: http://www.youtube.com/watch?v=jG7vhMMXagQ
-.. _Pi is wrong!: http://www.youtube.com/watch?v=IF1zcRoOVN0
-.. _a page of resources: http://www.math.utah.edu/~palais/pi.html
+.. _Tau Manifesto: https://tauday.com/
+.. _Pi is (still) wrong: https://vimeo.com/147792667
+.. _Pi is wrong!: https://www.youtube.com/watch?v=PIhNNnW1tUo
+.. _a page of resources: https://www.math.utah.edu/~palais/pi.html
 
 
 Copyright

peps/pep-0745.rst

@@ -48,10 +48,10 @@ Actual:
 - 3.14.0 beta 2: Monday, 2025-05-26
 - 3.14.0 beta 3: Tuesday, 2025-06-17
 - 3.14.0 beta 4: Tuesday, 2025-07-08
+- 3.14.0 candidate 1: Tuesday, 2025-07-22
 
 Expected:
 
-- 3.14.0 candidate 1: Tuesday, 2025-07-22
 - 3.14.0 candidate 2: Tuesday, 2025-08-26
 - 3.14.0 final: Tuesday, 2025-10-07
 

peps/pep-0747.rst

@@ -183,7 +183,7 @@ expression, and it represents the type described by that type expression.
 
 ``TypeForm`` is a special form that, when used in a type expression, describes
 a set of type form objects. It accepts a single type argument, which must be a
-valid type expression. ``TypeForm[T]`` describes the set of all type form
+:ref:`valid type expression <valid-type-expressions>`. ``TypeForm[T]`` describes the set of all type form
 objects that represent the type ``T`` or types that are
 :term:`assignable to <typing:assignable>` ``T``. For example,
 ``TypeForm[str | None]`` describes the set of all type form objects
@@ -218,9 +218,7 @@ equivalent to ``TypeForm[Any]``.
 Implicit ``TypeForm`` Evaluation
 --------------------------------
 
-When a static type checker encounters an expression that follows all of the
-syntactic, semantic and contextual rules for a type expression as detailed
-in the typing spec, the evaluated type of this expression should be assignable
+When a static type checker encounters a valid type expression, the evaluated type of this expression should be assignable
 to ``TypeForm[T]`` if the type it describes is assignable to ``T``.
 
 For example, if a static type checker encounters the expression ``str | None``,
@@ -248,6 +246,11 @@ be assignable to ``TypeForm``::
 
   v5: TypeForm[set[str]] = "set[str]"  # OK
 
+.. _valid-type-expressions:
+
+Valid Type Expressions
+----------------------
+
 The typing spec defines syntactic rules for type expressions in the form of a
 :ref:`formal grammar <typing:expression-grammar>`. Semantic rules are specified
 as comments along with the grammar definition. Contextual requirements are detailed
@@ -256,8 +259,11 @@ type expressions. For example, the special form ``Self`` can be used in a
 type expression only within a class, and a type variable can be used within
 a type expression only when it is associated with a valid scope.
 
-Expressions that violate one or more of the syntactic, semantic, or contextual
-rules for type expressions should not evaluate to a ``TypeForm`` type.::
+A valid type expression is an expression that follows all of the syntactic,
+semantic, and contextual rules for a type expression.
+
+Expressions that are not valid type expressions should not evaluate to a
+``TypeForm`` type::
 
   bad1: TypeForm = tuple()  # Error: Call expression not allowed in type expression
   bad2: TypeForm = (1, 2)  # Error: Tuple expression not allowed in type expression

peps/pep-0772.rst

@@ -11,6 +11,7 @@ Created: 21-Jan-2025
 Post-History:
   `06-Feb-2025 <https://discuss.python.org/t/pep-772-packaging-governance-process/79724/1>`__,
   `30-May-2025 <https://discuss.python.org/t/pep-772-packaging-council-governance-process-round-2/93904>`__,
+  `25-Jul-2025 <https://discuss.python.org/t/pep-772-packaging-council-governance-process-round-3/100181>`__,
 Replaces: 609
 
 
@@ -198,31 +199,31 @@ Election of the Packaging Council
 A Packaging Council election consists of the following phases:
 
 * **Phase 1**: Packaging Council Electors are determined by opt-in self-selection of the `PSF voting
-  members <voting-members>`_.  The PSF voting membership is informed that Packaging Council ballots
-  will be available, and any PSF voting member can request a ballot.  The PSF may choose to solicit
+  members`_.  The PSF voting membership is informed that Packaging Council ballots will be
+  available, and any PSF voting member can request a ballot.  The PSF may choose to solicit
   participation for both the PSF Board elections and Packaging Council elections at the same time.
   Packaging Council Electors retain their voting rights for the entire year, and may exercise such
   rights for other community-wide votes that may occur during that year.
 
 * **Phase 2**: Packaging Council Electors may nominate any individual for the Council election, including
-  themselves.  Nominees do not need to be PSF members, but nominations must include information
+  themselves.  Nominees must themselves be PSF voting members, and nominations must include information
   about the nominee's relevant affiliations.
 
 * **Phase 3**: Each Elector receives a ballot consisting of all eligible nominees, which Electors
-  use to cast their vote for the Packaging Council. They can assign zero to five stars to each
-  candidate.  Voting is performed anonymously. The outcome of the vote is determined using the `STAR
-  voting system`_, modified to use the `Multi-winner Bloc STAR`_ approach.  If a tie occurs, it may
-  be resolved by mutual agreement among the candidates, or else the winner will be chosen at random.
+  use to cast their vote for the Packaging Council.  The mechanics of the election (i.e. the
+  software used to conduct the election, the algorithm used to determine the outcome of the vote,
+  etc.) are conducted by the PSF, in accordance with the `PSF bylaws`_ and its regular Board
+  election procedures.  If a tie occurs, it may be resolved by mutual agreement among the
+  candidates, or else the winner will be chosen at random.
 
 Each phase will last two weeks.
 
-The Packaging Council election process is managed by a returns officer nominated by the Python
-Steering Council.  The PSF shall maintain records of the elections as well as run the annual
-election for the Packaging Council.  The Steering Council must certify the results of the election
-and may work with the returns officer in whatever capacity is necessary to validate the integrity of
-the election.  Election transparency being of paramount importance for trust in the process, full
-vote totals *before* any exclusions, while maintaining anonymity, should be made public when
-technically possible.
+The Packaging Council election process is managed by a returns officer nominated by the PSF Board.
+The PSF shall maintain records of the elections as well as run the annual election for the Packaging
+Council.  The PSF Board must certify the results of the election and may work with the returns
+officer in whatever capacity is necessary to validate the integrity of the election.  Election
+transparency being of paramount importance for trust in the process, full vote totals *before* any
+exclusions, while maintaining anonymity, should be made public when technically possible.
 
 Quorum for Packaging Council votes (either cohort election or votes of no confidence) is 50% of
 Electors.
@@ -243,6 +244,10 @@ original cohort.
 Each Council member's term will be two years, from when their elections are
 finalized until the next elections for their cohort are finalized.
 
+As Packaging Council elections will generally align with the timing of PSF Board elections, any
+members elected in an "off cycle" Council election (such as the initial Council election) will
+similarly serve until the next regular election for their cohort.
+
 .. _whole-council:
 
 Only for elections of the entire Packaging Council (such as the initial Council election), the two
@@ -266,8 +271,9 @@ If a Council member drops out of touch and cannot be contacted for a month or
 longer, then the rest of the Council may vote to replace them (with a simple
 majority vote, where the missing member is recorded as an abstention).
 
-If a full Packaging Council cannot be seated by this process, the Python Steering Council can appoint new
-Packaging Council members to fill the vacancies, or call for new Packaging Council elections.
+If a full Packaging Council cannot be seated by this process, the PSF Board, in consultation with
+the Python Steering Council, can appoint new Packaging Council members to fill the vacancies, or
+call for new Packaging Council elections.
 
 Conflicts of interest
 ---------------------
@@ -285,7 +291,7 @@ packaging development could itself be harmful and erode trust.
 
 PSF staff members are not permitted to serve as members of the Packaging Council.
 
-Currently serving Steering Council members are not permitted to concurrently serve as members of the Packaging
+Serving Steering Council members are not permitted to concurrently serve as members of the Packaging
 Council.
 
 In a Council election, if more than two of the top five vote-getters work for the same employer, then only the
@@ -294,9 +300,18 @@ elevated in the vote rank.  This process is repeated until a valid Packaging Cou
 process a full Council cannot be formed, disqualified vote-getters are re-qualified in the rank order of their
 vote tally until a full Council can be formed.
 
+If fewer than five members are to be elected, an analogous procedure is applied in order to
+guarantee that no more than two members of the entire Packaging Council work for the same employer.
+
 During a Packaging Council term, if changing circumstances cause this rule to be broken (for instance, due to
 a Council member changing employment), then one or more Council members must resign to remedy the issue, and
-the resulting vacancies can then be filled as `normal <vacancy>`_.
+the resulting vacancies can then be filled as :ref:`normal <vacancy>`.
+
+Code of Conduct
+---------------
+
+All Packaging Council Electors and Packaging Council members are subject to, and must abide by the
+PSF `Code of Conduct`_, its enforcement procedures, and its remedies for adjudicated violations.
 
 .. _electors:
 
@@ -311,10 +326,13 @@ Responsibilities
 Packaging Council Electors participate in formal votes to elect the Packaging Council.
 
 The eligibility of Packaging Council Electors is equivalent to the Article IV, section 4.2 voting
-membership defined in the `PSF Bylaws <https://www.python.org/psf/bylaws/>`_.  Should those bylaws
-change in the future, the eligibility of Packaging Council Electors will similarly change to match.
-As with PSF voting membership, Packaging Council Electors must affirm their intention to vote in
-Packaging Council elections every year.
+membership defined in the `PSF bylaws`_.  Should those bylaws change in the future, the eligibility
+of Packaging Council Electors will similarly change to match.  Packaging Council Electors must
+affirm their intention to vote in Packaging Council elections in a manner and process similar to PSF
+Board voting membership affirmations.
+
+PSF voting members may opt-out (annually or indefinitely) from Packaging Council elections
+independently of their choice to vote in PSF Board elections.
 
 .. _process:
 
@@ -325,19 +343,20 @@ Vote of no confidence
 ---------------------
 
 In exceptional circumstances, a vote of no confidence may be called to remove a sitting Packaging
-Council member, or the entire council.  The Python Steering Council may call such votes of no
+Council member, or the entire Council.  The Python Steering Council may call such votes of no
 confidence, with no second being necessary.  Anyone may request such a vote of no confidence from
 the Steering Council regardless of the requester's membership or affiliation, and the Steering
-Council has full discretion to call for the vote or not.
+Council has discretion to call for the vote or not.  The PSF Board may overrule the Steering Council
+to initiate a vote of no confidence.
 
 The vote of no confidence lasts for two weeks. Each Elector votes for or against. If at least two
 thirds of Electors express a lack of confidence, then the vote succeeds.
 
 There are two forms of no-confidence votes: those targeting a single member, and those targeting the Council
 as a whole. The initial call for a no-confidence vote must specify which type is intended. If a single-member
 vote succeeds, then that member is removed from the Council and the resulting vacancy can be handled by the
-`normal process <vacancy>`_. If a whole-Council vote succeeds, the Council is dissolved and a new Council
-election is triggered immediately, using the rules for `whole Council <whole-council>`_ elections.
+:ref:`normal process <vacancy>`. If a whole-Council vote succeeds, the Council is dissolved and a new Council
+election is triggered immediately, using the rules for :ref:`whole Council <whole-council>` elections.
 
 -----------------------
 Changing the governance
@@ -358,10 +377,8 @@ Steering Council's elections. This PEP uses a cohort-based model, derived from
 the PSF Board's elections which enables continuity of members across a changing
 Council.
 
-There is a trade-off between continuity of the Council and full reshuffles. This PEP
-takes the position that continuity will be more valuable for the Python
-Packaging domain, especially combined with the vote of no confidence, automatic
-removal of inactive voters, and regular elections.
+There is a trade-off between continuity of the Council and full reshuffles. This PEP takes the
+position that continuity will be more valuable for the Python Packaging ecosystem.
 
 -------------------------------
 Term limits for council members
@@ -390,11 +407,12 @@ on that work without paying any membership fee.
 Approval voting in the election
 -------------------------------
 
-An earlier non-public draft of this PEP used an approval voting process, which aligned with what :pep:`13`
-stated at the time of writing. The Python core team has changed their governance to use Bloc STAR and this PEP
-was updated to align with that for the same reasons as the core team's move to Bloc STAR: it better captures
-voter intention in the results.  It is also expected that the same election machinery can be used for both
-elections.
+An earlier non-public draft of this PEP used an approval voting process, which aligned with what
+:pep:`13` stated at the time of writing. The Python core team has changed their governance to use
+Bloc STAR, and this PEP was temporarily changed to use the same mechanism.  However, since Packaging
+Council elections will now be concurrent with PSF Board elections, with the same voting constituency
+(i.e. PSF voting membership), and administered by the same returns officer, this PEP was updated to
+align Packaging Council elections with PSF Board elections.
 
 ------------------------------------------------------------------
 Disallow multiple people from the same organization on the council
@@ -482,5 +500,6 @@ packaging user experience.
 .. _virtualenv: https://packaging.python.org/en/latest/key_projects/#virtualenv
 .. _Packaging Workgroup: https://wiki.python.org/psf/PackagingWG
 .. _User Success Workgroup: https://github.com/psf/user-success-wg/
-.. _STAR voting system: https://www.starvoting.org/
-.. _Multi-winner Bloc STAR: https://www.starvoting.org/multi_winner
+.. _PSF bylaws: https://www.python.org/psf/bylaws/
+.. _Code of Conduct: https://policies.python.org/python.org/code-of-conduct/
+.. _PSF voting members: https://www.python.org/psf/membership/

peps/pep-0782.rst

@@ -53,8 +53,8 @@ When creating a bytes string and the output size is unknown, one
 strategy is to allocate a short buffer and extend it (to the exact size)
 each time a larger write is needed.
 
-This strategy is inefficient because it requires to enlarge the buffer
-multiple timess. It's more efficient to overallocate the buffer the
+This strategy is inefficient because it requires enlarging the buffer
+multiple times. It's more efficient to overallocate the buffer the
 first time that a larger write is needed. It reduces the number of
 expensive ``realloc()`` operations which can imply a memory copy.
 

peps/pep-0788.rst

@@ -1,5 +1,5 @@
 PEP: 788
-Title: Interpreter References
+Title: PyInterpreterRef: Interpreter References in the C API
 Author: Peter Bierma <zintensitydev@gmail.com>
 Sponsor: Victor Stinner <vstinner@python.org>
 Discussions-To: https://discuss.python.org/t/93653