1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
|
# Release history
## trio-websocket 0.12.2 (2025-02-24)
### Fixed
- fix incorrect port when using a `wss://` URL without supplying an explicit
SSL context
## trio-websocket 0.12.1 (2025-02-17)
### Fixed
- fix omitted direct dependency on outcome
([#196](https://github.com/python-trio/trio-websocket/issues/196))
## trio-websocket 0.12.0 (2025-02-16)
### Fixed
- fix loss of context/cause on ExceptionGroup exceptions
([#191](https://github.com/python-trio/trio-websocket/issues/191))
### Changed
- support trio strict_exception_groups=True
- expand type annotations
- add ability to specify receive buffer size, including `None` to let trio choose
- drop support for Python 3.7
## trio-websocket 0.11.1 (2023-09-26)
### Changed
- remove exceptiongroup dependency for Python >= 3.11
## trio-websocket 0.10.4 (2023-09-06)
### Fixed
- fix client hang when connection lost just after remote closes
## trio-websocket 0.10.3 (2023-06-08)
### Fixed
- fixed exception when installed trio package version has a suffix like `+dev`
## trio-websocket 0.10.2 (2023-03-19)
### Fixed
- fixed a race condition where, just after a local-initiated close, the
`closed` attribute would be `None`, and `send_message()` would be silently
ignored (wsproto < 0.2.0) or leak a `LocalProtocolError` (wsproto >= 0.2.0)
rather than raise `ConnectionClosed`
([#158](https://github.com/python-trio/trio-websocket/issues/158))
## trio-websocket 0.10.1 (2023-03-18)
### Fixed
- `send_message()` is changed to raise `ConnectionClosed` when a close
handshake is in progress. Previously, it would silently ignore
the call, which was an oversight, given that `ConnectionClosed` is
defined to cover connections "closed or in the process of closing".
Notably, this fixes `send_message()` leaking a wsproto `LocalProtocolError`
with wsproto >= 1.2.0.
([#175](https://github.com/python-trio/trio-websocket/issues/175))
Released as a minor version increment, since code calling `send_message()`
is expected to handle `ConnectionClosed` anyway.
## trio-websocket 0.10.0 (2023-03-13)
### Fixed
- avoid MultiError warnings with trio >= 0.22
### Changed
- drop support for Python 3.5, 3.6
## trio-websocket 0.9.2 (2021-02-05)
### Fixed
- the server will now correctly close the TCP stream on a CloseConnection event
([#115](https://github.com/python-trio/trio-websocket/issues/115))
## trio-websocket 0.9.1 (2020-12-06)
### Fixed
- fix client open_websocket_url() when the URL path component is empty
([#148](https://github.com/python-trio/trio-websocket/issues/148))
## trio-websocket 0.9.0 (2020-11-25)
> **_NOTE:_** `wsaccel`, which was important for good performance of
>`wsproto <= 0.14`, has been dropped as a trio-websocket requirement. So
> ensure that your app either upgrades to `wsproto >= 0.15` or explicitly
> requires `wsaccel`.
### Changed
- allow dependency on recent `wsproto` versions
- eliminate `yarl`, `ipaddress`, and `wsaccel` dependencies
### Fixed
- avoid contributing to dropped exceptions during finalization.
(See Trio issue https://github.com/python-trio/trio/issues/1559 for background.)
## trio-websocket 0.8.1 (2020-09-22)
### Fixed
- reader task no longer raises unhandled exception on ClosedResourceError
([#134](https://github.com/python-trio/trio-websocket/issues/134))
- minor issues in example code, documentation, and type-hinting
## ...
|
