Tyler Goodlet 616192d853 Don't use async gen functions for the stream API ... As mentioned in prior commits there's currently a bug in Python that make async gens **not** task safe. Since this is the core cause of almost all recent problems, instead implement our own async iterator derivative of `trio.abc.ReceiveChannel` by wrapping a `trio._channel.MemoryReceiveChannel`. This fits more natively with the memory channel API in ``trio`` and adds potentially more flexibility for possible bidirectional inter-actor streaming in the future. Huge thanks to @oremanj and of course @njsmith for guidance on this one!		2019-02-15 21:59:42 -05:00
..
testing	Support `loglevel` fixture injection	2018-11-30 01:11:08 -05:00
__init__.py	Add a pub-sub messaging decorator API	2019-01-16 12:19:01 -05:00
_actor.py	Don't use async gen functions for the stream API	2019-02-15 21:59:42 -05:00
_exceptions.py	Change parent type	2019-01-12 17:55:28 -05:00
_forkserver_hackzorz.py	Woot! mypy run is clean!	2018-08-31 17:16:24 -04:00
_ipc.py	Make the `Context` a dataclass	2019-01-20 21:47:08 -05:00
_portal.py	Don't use async gen functions for the stream API	2019-02-15 21:59:42 -05:00
_state.py	Woot! mypy run is clean!	2018-08-31 17:16:24 -04:00
_trionics.py	Use local actor var	2019-02-15 17:11:26 -05:00
log.py	Oh, mypy...	2018-11-09 01:52:57 -05:00
msg.py	Do proper `wrapt` arg extraction for type checking	2019-01-25 00:10:13 -05:00