From 5871f57a426c9e498a317510a59ed39e0d2c6ba4 Mon Sep 17 00:00:00 2001 From: Brian Long Date: Mon, 19 May 2025 14:45:15 -0400 Subject: [PATCH 1/3] added first language for Python versions --- tutorials/pyproject-toml.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/tutorials/pyproject-toml.md b/tutorials/pyproject-toml.md index 1c0b75dd..ee0940bd 100644 --- a/tutorials/pyproject-toml.md +++ b/tutorials/pyproject-toml.md @@ -307,6 +307,14 @@ The `requires-python` field helps pip identify which Python versions that your p It is set to a single value. The [packaging specification](https://packaging.python.org/en/latest/specifications/core-metadata/#core-metadata-requires-python) defines`requires-python` as a string that uses version specifiers. Most projects will specify the oldest Python version supported by the package. In some advanced cases, an upper bound is set to indicate which future Python versions, if any, will be supported. +(python-version)= +#### Which Python versions to support? + +But how do I figure out which Python versions I should support? Good question. The Python developer guide provides a [status page](https://devguide.python.org/versions/) (and a handy visualization) that explains the status of each Python release. Python releases go through several different phases that are explained in [PEP 602](https://peps.python.org/pep-0602/). + +We recommend that you use the Python release that's in the **prerelease** phase, or the versions that are currently in the **bugfix** phase. If your Python release is in the **security** phase, we recommend migrating to a newer version of Python. + +[SPEC 0](https://scientific-python.org/specs/spec-0000/) of the Scientific Python project suggests a common schedule for dependencies, including Python release versions, and is also worth considering for your project. {emphasize-lines="22"} ```toml From 6d40a7ed7b390f092ffc2f066bd99ee3a0960637 Mon Sep 17 00:00:00 2001 From: Brian Long Date: Tue, 20 May 2025 11:43:10 -0400 Subject: [PATCH 2/3] changed admonition to tip class --- tutorials/pyproject-toml.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/tutorials/pyproject-toml.md b/tutorials/pyproject-toml.md index ee0940bd..083b9425 100644 --- a/tutorials/pyproject-toml.md +++ b/tutorials/pyproject-toml.md @@ -307,14 +307,14 @@ The `requires-python` field helps pip identify which Python versions that your p It is set to a single value. The [packaging specification](https://packaging.python.org/en/latest/specifications/core-metadata/#core-metadata-requires-python) defines`requires-python` as a string that uses version specifiers. Most projects will specify the oldest Python version supported by the package. In some advanced cases, an upper bound is set to indicate which future Python versions, if any, will be supported. -(python-version)= -#### Which Python versions to support? - -But how do I figure out which Python versions I should support? Good question. The Python developer guide provides a [status page](https://devguide.python.org/versions/) (and a handy visualization) that explains the status of each Python release. Python releases go through several different phases that are explained in [PEP 602](https://peps.python.org/pep-0602/). +:::{admonition} But how do I figure out which Python versions I should support? +:class: tip +Good question. The Python developer guide provides a [status page](https://devguide.python.org/versions/) (and a handy visualization) that explains the status of each Python release. Python releases go through several different phases that are explained in [PEP 602](https://peps.python.org/pep-0602/). -We recommend that you use the Python release that's in the **prerelease** phase, or the versions that are currently in the **bugfix** phase. If your Python release is in the **security** phase, we recommend migrating to a newer version of Python. +We recommend that you use the latest Python release in the **bugfix** phase. If your Python release is in the **security** phase, we recommend migrating to a newer version of Python. [SPEC 0](https://scientific-python.org/specs/spec-0000/) of the Scientific Python project suggests a common schedule for dependencies, including Python release versions, and is also worth considering for your project. +::: {emphasize-lines="22"} ```toml From 4347b76e119ddf9d31f8d08dfa96eaacc25ee3da Mon Sep 17 00:00:00 2001 From: "pre-commit-ci[bot]" <66853113+pre-commit-ci[bot]@users.noreply.github.com> Date: Tue, 20 May 2025 16:01:25 +0000 Subject: [PATCH 3/3] =?UTF-8?q?'[pre-commit.ci=20=F0=9F=A4=96]=20Apply=20c?= =?UTF-8?q?ode=20format=20tools=20to=20PR'?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- tutorials/pyproject-toml.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tutorials/pyproject-toml.md b/tutorials/pyproject-toml.md index 083b9425..dcdeca70 100644 --- a/tutorials/pyproject-toml.md +++ b/tutorials/pyproject-toml.md @@ -307,7 +307,7 @@ The `requires-python` field helps pip identify which Python versions that your p It is set to a single value. The [packaging specification](https://packaging.python.org/en/latest/specifications/core-metadata/#core-metadata-requires-python) defines`requires-python` as a string that uses version specifiers. Most projects will specify the oldest Python version supported by the package. In some advanced cases, an upper bound is set to indicate which future Python versions, if any, will be supported. -:::{admonition} But how do I figure out which Python versions I should support? +:::{admonition} But how do I figure out which Python versions I should support? :class: tip Good question. The Python developer guide provides a [status page](https://devguide.python.org/versions/) (and a handy visualization) that explains the status of each Python release. Python releases go through several different phases that are explained in [PEP 602](https://peps.python.org/pep-0602/).