From 4e3a91e03fe44f9079953292af48f38f112a1594 Mon Sep 17 00:00:00 2001 From: Matthew Feickert Date: Wed, 3 Mar 2021 15:15:24 -0600 Subject: [PATCH] fix: Remove '<4' from python_requires in packaging guide As discussed in https://discuss.python.org/t/use-of-less-than-next-major-version-e-g-4-in-python-requires-setup-py/1066 and other places there can be some side effects of adding `<4` to a library's python_requires. This PR removes it, as requested in the discuss.python question. The section above the lines discussed in the topic that uses compatible release syntax is also removed given that `~=3.3` also enforces `<4`. Additional references of problems known to Matthew for posterity: * Twitter threads: - https://twitter.com/HEPfeickert/status/1362170933658738701 - https://twitter.com/nicholdav/status/1366978826790666240 * GitHub Issues: - https://github.com/python-poetry/poetry/issues/3747 --- source/guides/distributing-packages-using-setuptools.rst | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/source/guides/distributing-packages-using-setuptools.rst b/source/guides/distributing-packages-using-setuptools.rst index b5f0f4222..af91c7c88 100644 --- a/source/guides/distributing-packages-using-setuptools.rst +++ b/source/guides/distributing-packages-using-setuptools.rst @@ -397,15 +397,10 @@ versions. For example, if your package is for Python 3+ only, write:: python_requires='>=3', -If your package is for Python 3.3 and up but you're not willing to commit to -Python 4 support yet, write:: - - python_requires='~=3.3', - If your package is for Python 2.6, 2.7, and all versions of Python 3 starting with 3.3, write:: - python_requires='>=2.6, !=3.0.*, !=3.1.*, !=3.2.*, <4', + python_requires='>=2.6, !=3.0.*, !=3.1.*, !=3.2.*', And so on.