Ok the question is a bit misleading as I was able to get it working pretty reliably on python 3.10, but I think this should be documented somewhere.

My ideal solution (which I already have implemented) is to migrate from using requirements.txt to pipenv, providing the following benefits:

• the python version in use is clearly written in the Pipfile
• Pipenv provides dependency locking via a lockfile, so its more reproducible and easier to collaborate with others on
• dependency updates are easier and dont require manually specifying exact versions. Instead versions can be set as "up to", and the lockfile can be used to ensure consistency. This makes dependency upgrades less of a manual conflict resolution hassle
• Pipenv reduces the number of commands that need to be listed in the README for users to run

As an alternative, I could also just update the README to mention the python version, but that isnt quite as ideal.

Wanted to open this issue to see what would be the preferred path