You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ASYNC102 no longer raises warning for calls to .aclose() on objects (#222)
* ASYNC102 no longer raises warning for calls to `.aclose()` on objects
* bump __version__
* fixes after review: allow aclose() in except clauses. Only allow if no args. Don't exempt asyncio-only code.
* lol I was so confused why this started failing
Copy file name to clipboardExpand all lines: CHANGELOG.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,11 @@
1
1
# Changelog
2
2
*[CalVer, YY.month.patch](https://calver.org/)*
3
3
4
+
## 24.3.5
5
+
- ASYNC102 (no await inside finally or critical except) no longer raises warnings for calls to `aclose()` on objects in trio/anyio code. See https://github.com/python-trio/flake8-async/issues/156
6
+
4
7
## 24.3.4
5
-
- ASYNC110 (don't loop sleep) now also warns if looping `[trio/anyio].lowlevel.checkpoint()`
8
+
- ASYNC110 (don't loop sleep) now also warns if looping `[trio/anyio].lowlevel.checkpoint()`.
0 commit comments