Update references to Python 3.7 in docs/
#2524
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
AvlWx2014
commented
Dec 28, 2023
docs/docs/usage/project.md
Outdated
| @@ -62,9 +62,9 @@ The value of `requires-python` is a [version specifier as defined in PEP 440](ht | |||
| | `>=3.7,<3.11` | Python 3.7, 3.8, 3.9 and 3.10 | | |||
| | `>=3.6,!=3.8.*,!=3.9.*` | Python 3.6 and above, except 3.8 and 3.9 | | |||
|
|
|||
| ## Working with Python < 3.7 | |||
| ## Working with Python <= 3.7 | |||
There was a problem hiding this comment.
@frostming is this paragraph still accurate with this change?
AvlWx2014
commented
Dec 28, 2023
|
|
||
| Although PDM run on Python 3.7 and above, you can still have lower Python versions for your **working project**. But remember, if your project is a library, which needs to be built, published or installed, you make sure the PEP 517 build backend being used supports the lowest Python version you need. For instance, the default backend `pdm-backend` only works on Python 3.7+, so if you run [`pdm build`](../reference/cli.md#build) on a project with Python 3.6, you will get an error. Most modern build backends have dropped the support for Python 3.6 and lower, so it is highly recommended to upgrade the Python version to 3.7+. Here are the supported Python range for some commonly used build backends, we only list those that support PEP 621 since otherwise PDM can't work with them. | ||
| Although PDM run on Python 3.8 and above, you can still have lower Python versions for your **working project**. But remember, if your project is a library, which needs to be built, published or installed, you make sure the PEP 517 build backend being used supports the lowest Python version you need. For instance, the default backend `pdm-backend` only works on Python 3.7+, so if you run [`pdm build`](../reference/cli.md#build) on a project with Python 3.6, you will get an error. Most modern build backends have dropped the support for Python 3.6 and lower, so it is highly recommended to upgrade the Python version to 3.7+. Here are the supported Python range for some commonly used build backends, we only list those that support PEP 621 since otherwise PDM can't work with them. |
There was a problem hiding this comment.
There's also a reference here, but I couldn't find anything for pdm-backend to suggest that Python 3.7 support has been dropped there, so I left this one.
AvlWx2014
force-pushed
the
AvlWx2014-update-python37-references
branch
from
8b4cb04 to
cfa253e
Compare
frostming
reviewed
Dec 28, 2023
AvlWx2014
force-pushed
the
AvlWx2014-update-python37-references
branch
from
844d708 to
88fda25
Compare
frostming
approved these changes
Jan 2, 2024
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Checklist
news/describing what is new.Describe what you have changed in this PR.
Drop references to Python 3.7 in docs/ files. I was reading the index page on
pdm-project.org/latestwhen I noticed that some vestigial references to Python 3.7 were still hanging around after the2.11.0release.There's also #2494, but it looks like that PR doesn't touch these files, only
ci.yml.