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.
I did some digging and it looked like maybe the workflows need to be updated, possibly due to the switch to Node16 instead of Node12 (https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/). It looked like the workflows were failing to even install python before running any tests on the package code.
I don't know anything about the workflows or how to test if this fixes anything. I just changed a few things based on the starter workflow from github's python package guide (https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-python).
Edit: the workflows failing in (#126) had errors about not finding python versions and warnings about the deprecation. I think the changes I am suggesting only address the warnings, not the errors.
Edit 2: based on this comment/thread (actions/setup-python#162 (comment)), the python 3.5 and 3.6 errors might be related to the
runs-on:ubuntu-latest
setting, as 3.5 and 3.6 don't include files for ubuntu version 22.04 (in the list of available versions https://raw.githubusercontent.com/actions/python-versions/main/versions-manifest.json).