Skip to content

Commit e88a088

Browse files
authored
Minor tweaks to new Requires-Python guide
- clarify minimum version requirement is for setuptools - minor markup fixes
1 parent 9cadc66 commit e88a088

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

source/guides/dropping-older-python-versions.rst

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -28,13 +28,13 @@ Defining the Python version required
2828
1. Download the newest version of Setuptools
2929
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3030

31-
Ensure that before you generate source distributions or binary distributions, you update Setuptools and twine.
31+
Ensure that before you generate source distributions or binary distributions, you update Setuptools and install twine.
3232

3333
Steps::
3434

3535
pip install --upgrade setuptools twine
3636

37-
Version should be above 24.0.0.
37+
`setuptools` version should be above 24.0.0.
3838

3939
2. Specify the version ranges for supported Python distributions
4040
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -49,7 +49,7 @@ Examples::
4949
The way to set those values is within the call to `setup` within your setup.py script. This will insert the Requires-Python
5050
metadata values based on the argument you provide in `python_requires`.
5151

52-
..code-block:: Python
52+
.. code-block:: python
5353
5454
from setuptools import setup
5555
@@ -67,7 +67,7 @@ Within a Python source package (the zip or the tar-gz file you download) is a te
6767
This file is generated by Distutils or :ref:`setuptools` when it generates the source package.
6868
The file contains a set of keys and values, the list of keys is part of the PyPa standard metadata format.
6969

70-
You can see the contents of the generated file like this:
70+
You can see the contents of the generated file like this::
7171

7272
tar xvfz dist/my-package-1.0.0.tar.gz -O | cat */PKG-INFO
7373

@@ -93,4 +93,4 @@ It must be done in this order for the automated fail-back to work.
9393
For example, you published the Requires-Python: ">=2.7" as version 1.0.0 of your package.
9494

9595
If you were then to update the version string to ">=3.5", and publish a new version 2.0.0 of your package, any users running Pip 9.0+ from version 2.7 will
96-
have version 1.0.0 of the package installed, and any >=3.5 users will receive version 2.0.0.
96+
have version 1.0.0 of the package installed, and any >=3.5 users will receive version 2.0.0.

0 commit comments

Comments
 (0)