Skip to content

Commit 6d40a7e

Browse files
committed
changed admonition to tip class
1 parent 5871f57 commit 6d40a7e

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

tutorials/pyproject-toml.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -307,14 +307,14 @@ The `requires-python` field helps pip identify which Python versions that your p
307307
It is set to a single value.
308308
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.
309309

310-
(python-version)=
311-
#### Which Python versions to support?
312-
313-
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/).
310+
:::{admonition} But how do I figure out which Python versions I should support?
311+
:class: tip
312+
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/).
314313

315-
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.
314+
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.
316315

317316
[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.
317+
:::
318318

319319
{emphasize-lines="22"}
320320
```toml

0 commit comments

Comments
 (0)