[Bug 1969902] Re: [SRU] Legacy API not compatible with Python 3.10 (Update to 10.x)

[Bastian Germann]

** Summary changed:

- Legacy API not compatible with Python 3.10 (Update to 10.x)
+ [SRU] Legacy API not compatible with Python 3.10 (Update to 10.x)

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1969902

Title:
  [SRU] Legacy API not compatible with Python 3.10 (Update to 10.x)

Status in rtpengine:
  Fix Released
Status in python-websockets package in Ubuntu:
  Fix Released
Status in python-websockets source package in Jammy:
  New

Bug description:
  [ Impact ]

  Currently we have python3-websockets version 9.1 in jammy's repo,
  which doesn't work with python3 version 3.10. python3-websockets
  version 10.2-1 is available in kinetic which fixes this. It should be
  made available via a SRU.

  [ Test Plan ]

  on jammy, get the GitHub tarball for 9.1 and run the tests:
  $ apt install python3-websockets
  $ wget https://github.com/aaugustin/websockets/archive/refs/tags/9.1.tar.gz
  $ tar xf 9.1.tar.gz
  $ cd websockets-9.1
  $ python3 -m unittest

  [ Where problems could occur ]

  The reverse dependencies are all building with the potential python-
  websockets 10.2-0ubuntu0.22.04.1 installed. python-hbmqtt fails but
  that is not a regression (see comments on this bug).

  10.2 includes the backwards-incompatible changes that are listed in 10.0's changelog:
  https://websockets.readthedocs.io/en/stable/project/changelog.html#id11

  These are the interesting ones:
  The signature of ConnectionClosed changed.
  A msg parameter was added to InvalidURI.

  Both of them are used by qiskit-ibmq-provider but in a 9.1/10.x
  compatible way.

To manage notifications about this bug go to:
https://bugs.launchpad.net/rtpengine/+bug/1969902/+subscriptions