-
Notifications
You must be signed in to change notification settings - Fork 94
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
deps: loosen pyzmq dependency #5307
Conversation
a5ca1d8
to
5c54c49
Compare
The Python 3.10 failure is a codecov upload failure, but the other two look like they might be real failures. |
The pyzmq package on conda-forge appears to be missing Python 3.7 builds, looking in... |
Conda-forge has dropped 3.7 - https://conda-forge.org/docs/user/announcements.html#dropping-python-3-7 This means new releases will not be built against 3.7. |
Options:
|
f484e24
to
5be8e69
Compare
12a38fe
to
c7a126d
Compare
I have changed tack on this PR and rolled #5311 into it avoiding the 3.7 issue |
* The ZMTP protocol provides robust forward & backward compatibility from libzmq version 3.2.2 onwards. * Since this is the minimum version compatible with pyzmq, we can safely loosen this version coupling. * For more information see the rationale in cylc#5311 (comment) * Closes cylc#5272 * Closes cylc#5311 * Unblocks cylc/cylc-uiserver#411
c7a126d
to
d72dad6
Compare
(rebased) |
Want me to have a look at the mypy failures? |
Presumably not related to this branch? |
Looks like it's type annotations added to newer versions of pyzmq |
Actually I think I already did this earlier, must have got lost in one of the force pushes, luckily I still had the branch locally |
tldr; We should be good to loosen off on this requirement, full rationale in the issue.