docs: update Changelog.

This commit is contained in:
David Wilson 2019-08-09 04:48:24 +01:00
parent 6fa69955c4
commit e352b9e5fd
1 changed files with 7 additions and 9 deletions

View File

@ -164,8 +164,8 @@ Core Library
`closed` flag, preventing historical bugs where a double close could destroy `closed` flag, preventing historical bugs where a double close could destroy
descriptors belonging to unrelated streams. descriptors belonging to unrelated streams.
* `#586 <https://github.com/dw/mitogen/issues/586>`_: fix import of the * `#586 <https://github.com/dw/mitogen/issues/586>`_: fix import of
`__main__` module on later versions of Python 3 when running from the :mod:`__main__` on later versions of Python 3 when running from the
interactive console. interactive console.
* `#606 <https://github.com/dw/mitogen/issues/606>`_: fix example code on the * `#606 <https://github.com/dw/mitogen/issues/606>`_: fix example code on the
@ -192,13 +192,11 @@ Core Library
* `5924af15 <https://github.com/dw/mitogen/commit/5924af15>`_: *[security]* the * `5924af15 <https://github.com/dw/mitogen/commit/5924af15>`_: *[security]* the
unidirectional routing mode, in which contexts may only communicate with unidirectional routing mode, in which contexts may only communicate with
their parents and never siblings (such that a program cannot be used as a parents and never siblings (so a program cannot accidentally bridge
bridge for air-gapped networks) was not inherited when a new child context air-gapped networks) was not inherited when a child context was initiated
was initiated directly from an existing child. directly from an existing child. This did not effect the Ansible extension,
since the controller initiates any new context used for routing, only forked
The bug did not effect the Ansible extension since the top-level controller tasks are initiated by children.
process initiates any new context that could be used for routing. Only
forked tasks are started directly from children.
Thanks! Thanks!