Closed musicinmybrain closed 3 years ago
Compare versions as tuples instead of strings, so that Python 3.10 is detected as >= Python 3.3.
Tests work on Python 3.10 instead of complaining that Python 3.3 or higher is needed.
CHANGES
<issue_id>.<type>
588.bugfix
issue_id
.feature
.bugfix
.doc
.removal
.misc
Fix issue with non-ascii contents in doctest text files.
Is all that documentation really needed for such a trivial fix?
What do these changes do?
Compare versions as tuples instead of strings, so that Python 3.10 is detected as >= Python 3.3.
Are there changes in behavior for the user?
Tests work on Python 3.10 instead of complaining that Python 3.3 or higher is needed.
Related issue number
Checklist
CHANGES
folder<issue_id>.<type>
(e.g.588.bugfix
)issue_id
change it to the pr id after creating the PR.feature
: Signifying a new feature..bugfix
: Signifying a bug fix..doc
: Signifying a documentation improvement..removal
: Signifying a deprecation or removal of public API..misc
: A ticket has been closed, but it is not of interest to users.Fix issue with non-ascii contents in doctest text files.
Is all that documentation really needed for such a trivial fix?