Fix python version in tests (plus additional minor fixes) #116
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.
Whilst looking into #115 I noticed that something funky was going in the CI environment when running tests in which a different python version from the ones specified in the version matrix, using python 3.10 for all of the tests.
This turned out to be because of the step in which space was being cleared, inadvertently deleting the python executable installed by the setup-python action at
/opt/hostedtoolscache
. I've replaced this with a different option using thejlumbroso/free-disk-space
action for ubuntu runners. Have tested this out over on my fork and confirmed that the expected python versions are being used in running tests by tox.Additionally, this PR: