community/py3-websockets-8.1-r3: test failure due to incorrect deprecation warnings

py3-websockets has test failures due to deprecation warnings:

======================================================================
FAIL: test_basic_auth (tests.test_auth.AuthClientServerTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/buildozer/aports/community/py3-websockets/src/websockets-8.1/tests/test_client_server.py", line 108, in _decorate
    with manager(self, *args, **kwargs):
  File "/usr/lib/python3.9/contextlib.py", line 119, in __enter__
    return next(self.gen)
  File "/home/buildozer/aports/community/py3-websockets/src/websockets-8.1/tests/test_client_server.py", line 72, in temp_test_server
    test.start_server(**kwargs)
  File "/home/buildozer/aports/community/py3-websockets/src/websockets-8.1/tests/test_client_server.py", line 248, in start_server
    self.assertDeprecationWarnings(recorded_warnings, expected_warnings)
  File "/home/buildozer/aports/community/py3-websockets/src/websockets-8.1/tests/utils.py", line 77, in assertDeprecationWarnings
    self.assertEqual(len(recorded_warnings), len(expected_warnings))
AssertionError: 2 != 0
[..]
----------------------------------------------------------------------
Ran 603 tests in 10.903s

FAILED (failures=174)
Test failed: <unittest.runner.TextTestResult run=603 errors=0 failures=174>
error: Test failed: <unittest.runner.TextTestResult run=603 errors=0 failures=174>
>>> ERROR: py3-websockets: check failed

This apparently is a bug in python 3.9.7, which is going to be fixed in python 3.9.8, mid November.

Upstream is aware of the problem as well.

We can do 2 things:

• Apply ustream patch
• Disable checks on py3-webscokets

type:buildozer-build-failure lang:python v3.15