Confirming this works. I could (with #962) pass test run on python3.9 / rhel8.4 machine.

Perhaps we should now add 3.9 to the python test matrix?

Perhaps we should now add 3.9 to the python test matrix?

My PR #954 makes it easier to test with multiple Python versions. Once the PR has landed, you can do py39-unit to run unit tests with Python 3.9.

Once the PR has landed, you can do py39-unit to run unit tests with Python 3.9.

That is very useful for local testing if developers think to do it. But I still think that if we claim to support python 3.9, then our ci build needs to confirm that via regular testing. One could add code which runs fine on 3.11 but not on 3.9 and we may not find this until much later than we could have known if the ci build tests on 3.9.

That is very useful for local testing if developers think to do it. But I still think that if we claim to support python 3.9, then our ci build needs to confirm that via regular testing. One could add code which runs fine on 3.11 but not on 3.9 and we may not find this until much later than we could have known if the ci build tests on 3.9.

You also need the change for CI to run tests with multiple Python versions. A common approach is tox-gh-action with a Python matrix and mapping of matrix env to tox env. The project documentation for tox-gh-action has documentation how to set up a test matrix.