You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The way to set those values is within the call to `setup` within your setup.py script. This will insert the Requires-Python
50
50
metadata values based on the argument you provide in `python_requires`.
51
51
52
-
..code-block:: Python
52
+
..code-block:: python
53
53
54
54
from setuptools import setup
55
55
@@ -67,7 +67,7 @@ Within a Python source package (the zip or the tar-gz file you download) is a te
67
67
This file is generated by Distutils or :ref:`setuptools` when it generates the source package.
68
68
The file contains a set of keys and values, the list of keys is part of the PyPa standard metadata format.
69
69
70
-
You can see the contents of the generated file like this:
70
+
You can see the contents of the generated file like this::
71
71
72
72
tar xvfz dist/my-package-1.0.0.tar.gz -O | cat */PKG-INFO
73
73
@@ -93,4 +93,4 @@ It must be done in this order for the automated fail-back to work.
93
93
For example, you published the Requires-Python: ">=2.7" as version 1.0.0 of your package.
94
94
95
95
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