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 PR deprecates Python 3.6, since this version has reached EOL (see link in changelog).
Python 3.9 and 3.10 are now supported versions.
All dependencies are upgraded to versions between Python 3.7 and 3.10.
Some flake8 fixes are included.
flake8
,pytest
,pytest bench
andcd docs && make html
was successfully executed with all now supported Python versions (3.7.13, 3.8.13, 3.9.13, 3.10.4). The benchmarks where not compared!The
audiomate.corpus.io
of the docs has gotten a bit bigger after upgrading Sphinx to the latest version.The bullets of ordered lists were hidden, but visible again after also upgrading
sphinx-rtd-theme
to the latest version.I didn't red the whole documentation 4 times (xD), but a quick look at all pages makes me feel like the docs looks fine.
This PR also fixes #83, though maybe a reference from the README could be added.
One Problem I observed with Python 3.7:
When installing the dev deps with
pip install -e .[dev]
and afterwards installing the ci deps withpip install -e .[ci]
(or vice versa) an error message is shown:In a ci environment this could be a problem when testing with pytest (Python version 3.7) and then linting with flake8.
During development this seems not to be a problem (flake8 and also pytest are running successfully despite the error).
When linting and testing (and the corresponding
pip install
) are executed in 2 different stages, the build should be run successfully since the error is only shown when.[ci]
and.[dev]
are executed consecutively.