-
-
Notifications
You must be signed in to change notification settings - Fork 77
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
Support python 3.11 #601
Support python 3.11 #601
Conversation
3505fa0
to
77501ba
Compare
77501ba
to
9349106
Compare
What does that do exactly? I'll have a closer look tomorrow but at first sight I'm not thrilled by having to split up the test workflow into three files, specially if we have to do that across many repos, as there's just more change for things to diverge when they're more scattered. But I don't know maybe it's the only way! |
It pins the python version, so it is not updated in the following
I'm not either, but I couldn't get it to work in a single file, and two (almost) identical files were a non-starter. I would love to have it in one file. |
Usually the issue I've seen with I think that unfortunately in this case this workaround wouldn't help :(
I'll try to see if there's another way. |
457b6dc
to
20469ba
Compare
20469ba
to
d8131e7
Compare
Add support for python 3.11. For now,
numba
is not installed on python 3.11 until it is compatible.I have split the test into two files, one which runs pull request, push etc., using python versions 3.7, 3.9 and 3.11. And a weekly test that also runs the versions in between.
I have also removed
actions/setup-python@v4
as it is not needed to run the test.At last I have added
echo $(python --version | tr ' [:upper:]' '=[:lower:]') > $CONDA_PREFIX/conda-meta/pinned
to the conda setup step to pin the python version.