@@ -1810,21 +1810,24 @@ functions and methods affected are :func:`~random.randrange`,
18101810poplib
18111811------
18121812
1813- * :class: `~poplib.POP3_SSL ` class now accepts a *context * parameter, which is a
1814- :class: `ssl.SSLContext ` object allowing bundling SSL configuration options,
1815- certificates and private keys into a single (potentially long-lived)
1816- structure.
1813+ :class: `~poplib.POP3_SSL ` class now accepts a *context * parameter, which is a
1814+ :class: `ssl.SSLContext ` object allowing bundling SSL configuration options,
1815+ certificates and private keys into a single (potentially long-lived)
1816+ structure.
1817+
1818+ (Contributed by Giampaolo Rodolà; :issue: `8807 `.)
18171819
1818- (Contributed by Giampaolo Rodolà; :issue: `8807 `.)
1820+ asyncore
1821+ --------
18191822
1820- * :class: `asyncore.dispatcher ` now provides a
1821- :meth: `~asyncore.dispatcher.handle_accepted() ` method
1822- returning a `(sock, addr) ` pair which is called when a connection has actually
1823- been established with a new remote endpoint. This is supposed to be used as a
1824- replacement for old :meth: `~asyncore.dispatcher.handle_accept() ` and avoids
1825- the user to call :meth: `~asyncore.dispatcher.accept() ` directly.
1823+ :class: `asyncore.dispatcher ` now provides a
1824+ :meth: `~asyncore.dispatcher.handle_accepted() ` method
1825+ returning a `(sock, addr) ` pair which is called when a connection has actually
1826+ been established with a new remote endpoint. This is supposed to be used as a
1827+ replacement for old :meth: `~asyncore.dispatcher.handle_accept() ` and avoids
1828+ the user to call :meth: `~asyncore.dispatcher.accept() ` directly.
18261829
1827- ( Contributed by Giampaolo Rodolà; :issue: `6706 `.)
1830+ Contributed by Giampaolo Rodolà; :issue: `6706 `.)
18281831
18291832tempfile
18301833--------
0 commit comments