-
Notifications
You must be signed in to change notification settings - Fork 27
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
Add Python 3.10 to CI builds #210
Add Python 3.10 to CI builds #210
Conversation
Indeed, looks like some dependency conflict due to the version pinning. |
I could be a problem of dependencies: Ensuring environment...
But then I cannot make any sense of the description of the conflicts. Conflicts are everywhere and it is not easy to pinpoint the root cause (I would bet on |
Fixed CI by removing version pinning here: Lines 26 to 27 in f3f1eb1
and here: z5/.github/workflows/environment.yaml Lines 12 to 14 in f3f1eb1
I don't know why version pinning is required and how you find the proper version to use. |
Thanks for looking into this!
The version pins are required because the xtensor projects have a fairly unstable API, so just installing the latest version is a bit dangerous. (Sorry that I realized this only now; just recalled that I had the same issues for the python 3.10 build on conda-forge half a year ago or so.) |
I have updated I don't know what to do with Lines 26 to 27 in f3f1eb1
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
(And the changes in the conda-recipe are fine; this one is deprecated and just left here for reference.)
No description provided.