Log message:
py-websockets: updated to 14.1

14.1
Unknown changes

Log message:
py-websockets: update to 14.0.

Changes not found.

Log message:
py-*: remove unused tool dependency

py-setuptools includes the py-wheel functionality nowadays

Log message:
py-websockets: updated to 13.0.1

13.0.1
Add provenance attestations.

Log message:
py-websockets: updated to 12.0

12.0

Backwards-incompatible changes

websockets 12.0 requires Python ≥ 3.8.

websockets 11.0 is the last version supporting Python 3.7.

Improvements

Made convenience imports from websockets compatible with static code analysis \ 
tools such as auto-completion in an IDE or type checking with mypy.
Accepted a plain :class:`int` where an :class:`~http.HTTPStatus` is expected.
Added :class:`~frames.CloseCode`.

Log message:
py-websockets: update to 11.0.3.

11.0.3

May 7, 2023

Bug fixes

    Fixed the threading implementation of servers on Windows.

11.0.2

April 18, 2023

Bug fixes

    Fixed a deadlock in the threading implementation when closing a connection \ 
without reading all messages.

11.0.1

April 6, 2023

Bug fixes

    Restored the C extension in the source distribution.

11.0

April 2, 2023

Backwards-incompatible changes

The Sans-I/O implementation was moved.

Aliases provide compatibility for all previously public APIs according to the \ 
backwards-compatibility policy.

    The connection module was renamed to protocol.

    The connection.Connection, server.ServerConnection, and \ 
client.ClientConnection classes were renamed to protocol.Protocol, \ 
server.ServerProtocol, and client.ClientProtocol.

Sans-I/O protocol constructors now use keyword-only arguments.

If you instantiate ServerProtocol or ClientProtocol directly, make sure you are \ 
using keyword arguments.

Closing a connection without an empty close frame is OK.

Receiving an empty close frame now results in ConnectionClosedOK instead of \ 
ConnectionClosedError.

As a consequence, calling WebSocket.close() without arguments in a browser \ 
isn’t reported as an error anymore.

serve() times out on the opening handshake after 10 seconds by default.

You can adjust the timeout with the open_timeout parameter. Set it to None to \ 
disable the timeout entirely.
New features

websockets 10.0 introduces a implementation on top of threading.

It may be more convenient if you don’t need to manage many connections and \ 
you’re more comfortable with threading than asyncio.

It is particularly suited to client applications that establish only one \ 
connection. It may be used for servers handling few connections.

See connect() and serve() for details.

    Added open_timeout to serve().

    Made it possible to close a server without closing existing connections.

    Added select_subprotocol to customize negotiation of subprotocols in the \ 
Sans-I/O layer.

Improvements

    Added platform-independent wheels.

    Improved error handling in broadcast().

    Set server_hostname automatically on TLS connections when providing a sock \ 
argument to connect().

Log message:
py-websockets: updated to 10.4

10.4

New features

Validated compatibility with Python 3.11.
Added the latency property to protocols.
Changed ping to return the latency of the connection.
Supported overriding or removing the User-Agent header in clients and the Server \ 
header in servers.
Added deployment guides for more Platform as a Service providers.

Improvements

Improved FAQ.

Log message:
py-websockets: updated to 10.3

10.3

Backwards-incompatible changes

The exception attribute of Request and Response is deprecated.
Use the handshake_exc attribute of ServerConnection and ClientConnection instead.
See Integrate the Sans-I/O layer for details.

Improvements

Reduced noise in logs when ssl or zlib raise exceptions.