-
Notifications
You must be signed in to change notification settings - Fork 7
/
Copy pathChangeLog
48 lines (38 loc) · 1.49 KB
/
ChangeLog
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
2.2.0:
- Typing fixes.
https://github.com/jsbronder/asyncio-dgram/issues/16
https://github.com/jsbronder/asyncio-dgram/issues/15
- Add option for resue_port in bind, thaks to yoelbassin.
https://github.com/jsbronder/asyncio-dgram/pull/14
- Support for python 3.11, 3.12 added.
- Support for python 3.5 dropped.
2.1.2:
- Do not default to AF_UNIX under windows. Thanks to jmarcet.
https://github.com/jsbronder/asyncio-dgram/pull/12
2.1.1:
- Fixed type-hint for DatagramStream's drained parameter. Thanks to
spumer for the report.
https://github.com/jsbronder/asyncio-dgram/issues/11
2.1.0:
- Type hints added
- DatagramStream.send() renamed to DatagramStream._send(). This should be
backward compatible as both DatagramServer and DatagramClient were
overloading it.
2.0.0:
- TransportClosed exception raised from send/recv if the other end hung
up. https://github.com/jsbronder/asyncio-dgram/issues/9
1.2.0:
- Added support for python 3.5
1.1.1:
- Add license to setup.py [Fabian Affolter]
1.1.0:
- AF_UNIX support added for python 3.7+
1.0.1:
- bind() no longer explicitly disables SO_REUSEADDR as upstream deprecated
the option.
1.0.0:
- bind() no longer sets SO_REUSEADDR by default. See upstream discussion
for rationale, https://bugs.python.org/issue37228
- DatagramStream.send() will now wait for the asyncio write buffer to
drain below the highwater mark before returning. This mimics the
forthcoming behavior from upstream, https://bugs.python.org/issue38242