Reconstruct some release history

Author: oremanj

docs/source/history.rst

@@ -21,6 +21,11 @@ Bugfixes
 - Calling ``loop.stop`` manually no longer causes a deadlock when
   exiting the context of ``trio_asyncio.open_loop`` (`#58 <https://github.com/python-trio/trio-asyncio/issues/58>`__)
 
+- :func:`trio_asyncio.run` now properly returns whatever was returned by
+  the async function it ran, like :func:`trio.run` does. (`#57 <https://github.com/python-trio/trio-asyncio/issues/57>`__)
+
+- Replace uses of deprecated ``trio.open_cancel_scope()`` with `trio.CancelScope`.
+
 Deprecations and Removals
 ~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -50,18 +55,21 @@ Bugfixes
 trio-asyncio 0.9.1 (2018-09-06)
 -------------------------------
 
+Bugfixes
+~~~~~~~~
+
+- Defer creating an asyncio coroutine until asyncio mode is actually entered. (`#40 <https://github.com/python-trio/trio-asyncio/issues/40>`__)
+
+trio-asyncio 0.9.0 (2018-08-31)
+-------------------------------
+
 Features
 ~~~~~~~~
 
 - **Major reorganization:** The main entry point for calling asyncio
   from trio is now the :func:`trio_asyncio.aio_as_trio` adapter.
   Instead of calling :func:`asyncio.get_event_loop`, directly access the
-  contextvar ``trio_aio_loop`` (aka :var:`trio_asyncio.adapter.current_loop`). (`#36 <https://github.com/python-trio/trio-asyncio/issues/36>`__)
-
-Bugfixes
-~~~~~~~~
-
-- Defer creating an asyncio coroutine until asyncio mode is actually entered. (`#40 <https://github.com/python-trio/trio-asyncio/issues/40>`__)
+  contextvar ``trio_aio_loop`` (aka :data:`trio_asyncio.current_loop`). (`#36 <https://github.com/python-trio/trio-asyncio/issues/36>`__)
 
 Deprecations and Removals
 ~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -83,28 +91,22 @@ Deprecations and Removals
   :func:`aio_as_trio`. (`#36
   <https://github.com/python-trio/trio-asyncio/issues/36>`__)
 
-trio-asyncio 0.8.4 (2018-08-25)
--------------------------------
-
-trio-asyncio 0.8.3 (2018-08-25)
--------------------------------
-
 trio-asyncio 0.8.2 (2018-08-25)
 -------------------------------
 
-trio-asyncio 0.8.1 (2018-08-25)
--------------------------------
+Features
+~~~~~~~~
 
-trio-asyncio 0.8.0 (2018-08-03)
--------------------------------
+- :func:`sniffio.current_async_library` in a trio-asyncio program now returns
+  the correct value for the current mode (``"trio"`` or ``"asyncio"``).
 
 trio-asyncio 0.8.1 (2018-08-25)
 -------------------------------
 
 Features
 ~~~~~~~~
 
-- `trio_asyncio` now contains an `allow_asyncio` wrapper which allows you to
+- `trio_asyncio` now contains an :func:`allow_asyncio` wrapper which allows you to
   seamlessly mix asyncio and trio semantics::
 
       import asyncio
@@ -122,10 +124,86 @@ Features
   code. This may or may not be an issue for your code. (`#30
   <https://github.com/python-trio/trio-asyncio/issues/30>`__)
 
+- While the test suite still requires Python 3.6, :mod:`trio_asyncio` itself
+  now works on Python 3.5.3 and later. (`#33
+  <https://github.com/python-trio/trio-asyncio/issues/33>`__)
 
-Bugfixes
-~~~~~~~~
+- ``TrioEventLoop.run_asyncio()`` now supports wrapping async iterators
+  and async context managers, in addition to its existing support for async
+  functions.
+
+trio-asyncio 0.8.0 (2018-08-03)
+-------------------------------
+
+* Add ``TrioEventLoop.run_iterator()`` as an alias for ``run_generator()``.
+
+* Add support for Python 3.7 via a monkey-patch to
+  :func:`asyncio.set_event_loop_policy`. (`#23
+  <https://github.com/python-trio/trio-asyncio/issues/23>`__)
+
+* Deprecate the use of "compatibility mode" / "sync event loops", except
+  as a tool for running the test suites of existing asyncio projects.
+
+trio-asyncio 0.7.5 (2018-07-23)
+-------------------------------
+
+* Use a contextvar to represent the current trio-asyncio loop, rather
+  than the deprecated ``trio.TaskLocal``.
+
+* Use the ``outcome`` library rather than the deprecated ``trio.hazmat.Result``.
+
+* Better handle errors in wrapped async generators.
+
+trio-asyncio 0.7.0 (2018-03-27)
+-------------------------------
+
+* The ``@trio2aio`` and ``@aio2trio`` decorators now can be used to decorate
+  both async generator functions and async functions that take keyword
+  arguments.
+
+* :func:`open_loop` now takes an optional ``queue_len=`` parameter to specify
+  the length of the internal callback queue (for performance tuning).
+
+* Add :meth:`BaseTrioEventLoop.synchronize`.
+
+* Monkey-patch :func:`asyncio.get_event_loop_policy` and
+  :func:`asyncio.get_event_loop` so trio-asyncio works correctly in
+  multithreaded programs that use a different asyncio event loop in
+  other threads.
+
+* Add ``wrap_generator()`` and ``run_generator()`` which adapt an asyncio-flavored
+  async generator to be used from Trio code.
+
+trio-asyncio 0.5.0 (2018-02-20)
+-------------------------------
+
+* Support contextvars on Python 3.7 and later.
+
+* Support waiting for child processes even though Trio doesn't (yet).
+
+trio-asyncio 0.4.2 (2018-02-12)
+-------------------------------
+
+* Add :func:`trio_asyncio.run`.
+
+* Fix a deadlock in ``SyncTrioEventLoop``. Encourage people to use the
+  async ``TrioEventLoop`` instead.
+
+trio-asyncio 0.4.1 (2018-02-08)
+-------------------------------
+
+* Add ``TrioEventLoop.run_task()`` as an entry point for running Trio code
+  in a context that allows asyncio calls, for use when neither a Trio nor
+  an asyncio event loop is running.
+
+trio-asyncio 0.4.0 (2018-02-07)
+-------------------------------
+
+* Add support for async loops (:func:`open_loop`) and encourage their use.
+  Numerous functions renamed.
+  
+trio-asyncio 0.3.0 (2017-10-17)
+-------------------------------
+
+* Initial release.
 
-- The test suite requires Python 3.6. :mod:`trio_asyncio` itself requires
-  Python 3.5.3. (`#33
-  <https://github.com/python-trio/trio-asyncio/issues/33>`__)