Document cross-project Python support policy #200
Conversation
booxter
force-pushed
the
python-version-support
branch
from
866eb28 to
9d429bf
Compare
Signed-off-by: Ihar Hrachyshka <[email protected]>
booxter
force-pushed
the
python-version-support
branch
from
9d429bf to
714cfd1
Compare
|
This pull request has been automatically marked as stale because it has not had activity within 30 days. It will be automatically closed if no further activity occurs within 7 days. |
| should be made to get back to the single dominant version as soon as possible, | ||
| to avoid wasting resources. | ||
|
|
||
| At the moment of writing, the dominant Python version is 3.11. |
There was a problem hiding this comment.
We can merge this this way, but we're going to want to very quickly make it 3.12.
There was a problem hiding this comment.
That was the plan and I wanted to split concerns - documentation of general approach using status quo and bumping versions.
There was a problem hiding this comment.
That definitely makes sense. 👍🏼
| version indicated above. | ||
|
|
||
| To drop support for a Python version, projects should remove all tests that are | ||
| specific to this version. They should also update `pyproject.yaml` metadata to |
There was a problem hiding this comment.
I have found https://pypi.org/project/check-python-versions/ to be helpful for listing this sort of thing to ensure packaging data and test jobs are consistent.
|
Feel free to post it as a new PR if still needed. |
3 participants
Signed-off-by: Ihar Hrachyshka [email protected]