From 7612ca4490973566a6bacab1fa25f9337fd40a0e Mon Sep 17 00:00:00 2001 From: Jelle Zijlstra Date: Thu, 11 Jan 2024 08:08:24 -0800 Subject: [PATCH] Reorder, don't always need conformance test changes --- docs/spec/meta.rst | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/spec/meta.rst b/docs/spec/meta.rst index b80c581c6..46f23217a 100644 --- a/docs/spec/meta.rst +++ b/docs/spec/meta.rst @@ -22,19 +22,20 @@ Changes to the specification come in three kinds: the `python/typing `__ repository, and may be merged by anyone with commit access. Such changes may include formatting fixes, linking improvements, etc. +- Substantive changes that do not rise to the level of a PEP must + be approved by the Typing Council. The procedure is described below. - Major changes should go through the PEP process, as described in :pep:`1`. What counts as a major change is not precisely defined, but it would generally include any change of a similar magnitude to `previous typing PEPs `__. -- Substantive changes that do not rise to the level of a PEP must - be approved by the Typing Council. The procedure is described below. Changes that need Typing Council approval go through three steps: - Open a discussion on `discuss.python.org `__ describing the issue. - Open a PR on `python/typing `__ - that changes the spec and the `conformance test suite `__. + that changes the spec and, if applicable, the + `conformance test suite `__. - `Open an issue `__ on the Typing Council's issue tracker asking for a decision.