transition from aiozmq -> pyzmq

Open
#166 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
backend, networking

Research direction

Start by reading issue 162 and locating the aiozmq usage in the repository. Compare the required pyzmq interface with the existing calls, then run the affected tests, focusing on teardown and calls made in quick succession. Done means the dependency transition is complete and socket connections close reliably during those tests.

Written by the indexing model from the issue text.

Description

This relates to https://github.com/dls-controls/tickit/issues/162

aiozmq had it's last release in 2020 and according to it's own docs supports up to python 3.8. It has no CI.

This might explain why we've been having difficulty tearing down tests, as the problem seems to be that the socket connections aren't properly closed for calls made in quick succession.

Dominant language
Python
Stars
7
Forks
1
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DiamondLightSource/tickit

All issues in DiamondLightSource/tickit

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.