New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test and mypy fixes. Add support for Python 3.11 #312
Conversation
|
For that you'd need to either change
That line is redundant since |
Taking advice from Nicola in #312.
Should I try to rebase this, given the conflicts generated by #315, or just close it? |
Doh - sorry. I assumed you had given up on the PR because I wanted to support 3.6. If you'd like to rebase that would be wonderful, but I made the mess and I'd be happy to pull out the 3.11 support and the tox refactorings and apply them in isolation. |
I can rebase, hopefully in the next days, no worries. |
bdb3cee
to
fb80358
Compare
Rebased and ready for re-review. |
Is the latest kombu not being compatible with python 3.6 a good enough reason to drop it ? (https://github.com/galaxyproject/pulsar/actions/runs/4678097934/jobs/8286413656?pr=323). That kombu version seems to have some important timeout handling fixes (https://github.com/celery/kombu/releases/tag/v5.2.3) |
BTW, the PR title had become misleading (fixed now), this is not removing Python 3.6 support any more given @jmchilton's concerns (I am still obviously in favour of dropping it). |
- Don't use hyphens in the middle of an environment name, they are used to split them in factors. - Simplify
Test on Python 3.6 and 3.11 without all intermediate versions. Also: - Remove install of `python-pycurl` in GitHub workflow, `pycurl` is installed later via tox without having to keep track of Ubuntu package name changes.
It feels like Pulsar has a lot of modalities that won't require that kombu fix so I'm in favor of continuing to support Python 3.6. The whole purpose of Pulsar originally was allowing the execution of Galaxy jobs in places Galaxy couldn't run - I'm not eager to remove environments. |
Planemo tests still fail on the py37-install_wheel build, but I don't know enough about those to fix it.
I think these are still good fixes and could probably be merged nonetheless?