feat: add Python 3.11 support#157
Merged
Merged
Conversation
This change coincides with the release of Python 3.11, which happened
24 OCT 2022. Anyone tracking this repository and this change should
update their use of `pyenv` locally, to include py3.11.x
A number of changes were made:
* Update the Docker base image version
* Update the CONTRIBUTING documentation
* Include lockfile checks in workflow steps
* This will provide a CI failure if the lockfile does not correspond
to the current version of the `pyproject.toml` file
* Failures could indicate a manual or improperly updated lockfile,
which could indicate malicious behavior
* Update the testing environments in `tox`, workflows, and unit tests
* Update `pyproject.toml` and generate an updated `poetry.lock` lockfile
* Add a new classifier
* Change from "caret" to specific range for supported Python versions
* `poetry-core` v1.3.2 is a new minimum requirement, given that Python
3.11 was added to the list of available Python versions
[in that release](https://github.com/python-poetry/poetry/releases/tag/1.2.2)
* Add package download count badges to the main README
Closes #150
Phylum OSS Supply Chain Risk Analysis - SUCCESSThe Phylum risk analysis is complete and did not identify any issues. |
This change aggregates all the test jobs into the "test rollup" job so that there will only be one job name that needs to be specified in the repository settings for branch protection and required status checks. The advantage of doing this is that the name of the status check will not change when the version of Python the underlying jobs use changes.
andreaphylum
approved these changes
Nov 4, 2022
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This change coincides with the release of Python 3.11, which happened 24 OCT 2022. Anyone tracking this repository and this change should update their use of
pyenvlocally, to include py3.11.xA number of changes were made:
pyproject.tomlfiletox, workflows, and unit testspyproject.tomland generate an updatedpoetry.locklockfile^3.7caret form was getting translated to>=3.7,<4.0, which meant that Python 3.11 was getting included as a supported version as soon as it was released...before testing and explicit adoption could happenpoetry-corev1.3.2 is a new minimum requirement, given that Python 3.11 was added to the list of available Python versions in that releaseCloses #150
Checklist
closes #<issueNum>in description above)?