Run tests with multiple Python versions #315
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
frej
force-pushed
the
frej/run-tests-with-different-python-versions
branch
3 times, most recently
from
e353d41
to
ec9453e
Compare
|
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
frej
force-pushed
the
frej/run-tests-with-different-python-versions
branch
24 times, most recently
from
ee4d7ec
to
e869039
Compare
Add `--debug` command line flag which dumps the detected versions of Mercurial and Python. This will probably help future debugging when unexpected versions are used.
Due to problems with handling of Unicode input in Python < 3.7, bump the required version of Python to 3.7.
Check that hg-fast-export is running on a supported version of Python on startup. This is an attempt to avoid problems like #314 in the future.
Run the CI tests with both the earliest supported Python version and the latest stable release. The intent is to quickly notice when new features require adjusting the oldest supported Python version and also detect when the latest stable version breaks old code (as when 3.12 removed `imp` and we witched to `importlib` in #311).
frej
force-pushed
the
frej/run-tests-with-different-python-versions
branch
from
e869039
to
2476d08
Compare
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.
Run the CI tests with both the earliest supported Python version and the latest stable release.
The intent is to quickly notice when new features require adjusting the oldest supported Python version and also detect when the latest stable version breaks old code (as when 3.12 removed
impand we switched toimportlibin #311).