To ensure visdom works with the recent versions, this PR does the following:
Adding the minimal required version (3.8) to setup.py which adds the requirement to pip.
Extending the functional tests to include all minor python version starting with the minimal version. Thus, the matrix of tests covers after this PR python3.8, python3.9, python3.10, python3.11.
How Has This Been Tested?
Tested the change successfully on top of #908.
(I.e. without #908 in-place, thus failing tests are expected until that one is merged)
Types of changes
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Code refactor or cleanup (changes to existing code for improved readability or performance)
Checklist:
[ ] I adapted the version number under py/visdom/VERSION according to Semantic Versioning
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
Description
Just a short housekeeping-PR with the goal to ensure visdom works on the most recent python versions.
Motivation and Context
I've chosen the oldest version to be python 3.8, as 3.7 will end support in the next months.
To ensure visdom works with the recent versions, this PR does the following:
3.8) tosetup.pywhich adds the requirement to pip.How Has This Been Tested?
Tested the change successfully on top of #908. (I.e. without #908 in-place, thus failing tests are expected until that one is merged)
Types of changes
Checklist:
py/visdom/VERSIONaccording to Semantic Versioning