Skip to content

Commit 8e6f8ea

Browse files
committed
Run towncrier and bump version to 0.14.1 for release
1 parent dde84b3 commit 8e6f8ea

File tree

4 files changed

+28
-5
lines changed

4 files changed

+28
-5
lines changed

Diff for: docs/source/history.rst

+27
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,33 @@ Release history
55

66
.. towncrier release notes start
77
8+
trio-asyncio 0.14.1 (2024-04-18)
9+
--------------------------------
10+
11+
Bugfixes
12+
~~~~~~~~
13+
14+
- ``TrioExecutor.submit()``, which implements calls to
15+
:meth:`asyncio.loop.run_in_executor` in a trio-asyncio program,
16+
no longer acquires a token from its `~trio.CapacityLimiter` before
17+
calling :func:`trio.to_thread.run_sync`.
18+
The previous behaviour caused each worker thread to consume two tokens
19+
rather than one, since :func:`trio.to_thread.run_sync` also acquires a token.
20+
When many tasks called :meth:`~asyncio.loop.run_in_executor` in parallel,
21+
this could cause a deadlock: because everyone is holding a first token, no one
22+
can make progress by getting a second one.
23+
(`#143 <https://github.com/python-trio/trio-asyncio/issues/143>`__)
24+
25+
26+
Miscellaneous
27+
~~~~~~~~~~~~~
28+
29+
- Updated test suite to cope with Trio 0.25.0 and later defaulting
30+
``strict_exception_groups`` to ``True``. Trio 0.25.0 is now required
31+
to run the tests, although trio-asyncio itself still supports older
32+
versions. (`#146 <https://github.com/python-trio/trio-asyncio/issues/146>`__)
33+
34+
835
trio-asyncio 0.14.0 (2024-02-07)
936
--------------------------------
1037

Diff for: newsfragments/143.bugfix.rst

-3
This file was deleted.

Diff for: newsfragments/146.misc.rst

-1
This file was deleted.

Diff for: trio_asyncio/_version.py

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,3 @@
11
# This file is imported from __init__.py and exec'd from setup.py
22

3-
__version__ = "0.14.0+dev"
3+
__version__ = "0.14.1"

0 commit comments

Comments
 (0)