Skip to content
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

Merged
merged 2 commits into from
Feb 14, 2023
Merged

Conversation

oliver-sanders
Copy link
Member

@oliver-sanders oliver-sanders commented Jan 17, 2023

tldr; We should be good to loosen off on this requirement, full rationale in the issue.

  • The ZMTP protocol provides robust forward & backward compatibilit 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 zmq: consider loosening version constraints #5311 (comment)

@oliver-sanders oliver-sanders added this to the cylc-8.2.0 milestone Jan 17, 2023
@oliver-sanders oliver-sanders self-assigned this Jan 17, 2023
@wxtim
Copy link
Member

wxtim commented Jan 17, 2023

The Python 3.10 failure is a codecov upload failure, but the other two look like they might be real failures.

@oliver-sanders
Copy link
Member Author

The pyzmq package on conda-forge appears to be missing Python 3.7 builds, looking in...

@oliver-sanders
Copy link
Member Author

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.

@oliver-sanders
Copy link
Member Author

Options:

  1. Build the swarm against "3.8" for "3.7" testing.
    Fine, but it does mean that the remote code won't get tested with 3.7.
  2. Drop "3.7".
    Fine but it is a little early, 3.7 doesn't hit end of life until June.

conda-environment.yml Outdated Show resolved Hide resolved
@oliver-sanders oliver-sanders marked this pull request as draft January 18, 2023 10:43
@oliver-sanders oliver-sanders force-pushed the bump-dependencies branch 2 times, most recently from f484e24 to 5be8e69 Compare February 2, 2023 17:10
@oliver-sanders oliver-sanders changed the title bump dependencies deps: loosen pyzmq dependency Feb 2, 2023
@oliver-sanders oliver-sanders marked this pull request as ready for review February 2, 2023 17:17
@oliver-sanders
Copy link
Member Author

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
@oliver-sanders
Copy link
Member Author

(rebased)

@MetRonnie
Copy link
Member

Want me to have a look at the mypy failures?

@oliver-sanders
Copy link
Member Author

Presumably not related to this branch?

@MetRonnie
Copy link
Member

Looks like it's type annotations added to newer versions of pyzmq

@MetRonnie
Copy link
Member

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

@MetRonnie MetRonnie merged commit c817dd9 into cylc:master Feb 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

zmq: consider loosening version constraints pyzmq: upgrade
3 participants