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
update error descriptions in README to better reflect which errors work with which library, and minor updates. 102/103/104 now sees asyncio.exceptions.CancelledError as a critical exception. Fix import/arg detection of asyncio. add asyncio102_asyncio. add async103_all_imported. Finally make test_anyio_from_config autodetect the correct line number. Fix BASE_LIBRARY marker being interpreted as a bool. Make #NOTRIO/#NOASYNCIO/#NOANYIO run the visitor but ignore the result, instead of skipping, to check it doesn't crash. Generalize error-message-library-check.
Copy file name to clipboardExpand all lines: README.md
+23-23
Original file line number
Diff line number
Diff line change
@@ -23,47 +23,47 @@ pip install flake8-async
23
23
```
24
24
25
25
## List of warnings
26
-
27
-
-**ASYNC100**: A `with trio.fail_after(...):` or `with trio.move_on_after(...):`
26
+
-**ASYNC100**: A `with [trio|anyio].fail_after(...):` or `with [trio|anyio].move_on_after(...):`
28
27
context does not contain any `await` statements. This makes it pointless, as
29
28
the timeout can only be triggered by a checkpoint.
30
-
-**ASYNC101**: `yield` inside a nursery or cancel scope is only safe when implementing a context manager - otherwise, it breaks exception handling.
31
-
-**ASYNC102**: It's unsafe to await inside `finally:` or `except BaseException/trio.Cancelled` unless you use a shielded
32
-
cancel scope with a timeout.
33
-
-**ASYNC103**: `except BaseException`, `except trio.Cancelled` or a bare `except:` with a code path that doesn't re-raise. If you don't want to re-raise `BaseException`, add a separate handler for `trio.Cancelled` before.
34
-
-**ASYNC104**: `Cancelled` and `BaseException` must be re-raised - when a user tries to `return` or `raise` a different exception.
35
-
-**ASYNC105**: Calling a trio async function without immediately `await`ing it.
29
+
-**ASYNC101**: `yield` inside a trio/anyio nursery or cancel scope is only safe when implementing a context manager - otherwise, it breaks exception handling.
30
+
-**ASYNC102**: It's unsafe to await inside `finally:` or `except BaseException/trio.Cancelled/anyio.get_cancelled_exc_class()/asyncio.exceptions.CancelledError` unless you use a shielded cancel scope with a timeout. This is currently not able to detect asyncio shields.
31
+
-**ASYNC103**: `except BaseException/trio.Cancelled/anyio.get_cancelled_exc_class()/asyncio.exceptions.CancelledError`, or a bare `except:` with a code path that doesn't re-raise. If you don't want to re-raise `BaseException`, add a separate handler for `trio.Cancelled`/`anyio.get_cancelled_exc_class()`/`asyncio.exceptions.CancelledError` before.
32
+
-**ASYNC104**: `trio.Cancelled`/`anyio.get_cancelled_exc_class()`/`asyncio.exceptions.CancelledError`/`BaseException` must be re-raised. The same as ASYNC103, except specifically triggered on `return` or a different exception being raised.
33
+
-**ASYNC105**: Calling a trio async function without immediately `await`ing it. This is only supported with trio functions, but you can get similar functionality with a type-checker.
36
34
-**ASYNC106**: `trio`/`anyio`/`asyncio` must be imported with `import trio`/`import anyio`/`import asyncio` for the linter to work.
37
-
-**ASYNC109**: Async function definition with a `timeout` parameter - use `trio.[fail/move_on]_[after/at]` instead
38
-
-**ASYNC110**: `while <condition>: await trio.sleep()` should be replaced by a `trio.Event`.
35
+
-**ASYNC109**: Async function definition with a `timeout` parameter - use `[trio/anyio].[fail/move_on]_[after/at]` instead.
36
+
-**ASYNC110**: `while <condition>: await [trio/anyio].sleep()` should be replaced by a `[trio|anyio].Event`.
39
37
-**ASYNC111**: Variable, from context manager opened inside nursery, passed to `start[_soon]` might be invalidly accessed while in use, due to context manager closing before the nursery. This is usually a bug, and nurseries should generally be the inner-most context manager.
40
38
-**ASYNC112**: Nursery body with only a call to `nursery.start[_soon]` and not passing itself as a parameter can be replaced with a regular function call.
41
39
-**ASYNC113**: Using `nursery.start_soon` in `__aenter__` doesn't wait for the task to begin. Consider replacing with `nursery.start`.
42
40
-**ASYNC114**: Startable function (i.e. has a `task_status` keyword parameter) not in `--startable-in-context-manager` parameter list, please add it so ASYNC113 can catch errors when using it.
43
-
-**ASYNC115**: Replace `trio.sleep(0)` with the more suggestive `trio.lowlevel.checkpoint()`.
44
-
-**ASYNC116**: `trio.sleep()` with >24 hour interval should usually be `trio.sleep_forever()`.
41
+
-**ASYNC115**: Replace `[trio|anyio].sleep(0)` with the more suggestive `[trio|anyio].lowlevel.checkpoint()`.
42
+
-**ASYNC116**: `[trio|anyio].sleep()` with >24 hour interval should usually be `[trio|anyio].sleep_forever()`.
45
43
-**ASYNC118**: Don't assign the value of `anyio.get_cancelled_exc_class()` to a variable, since that breaks linter checks and multi-backend programs.
46
44
47
45
### Warnings for blocking sync calls in async functions
48
-
-**ASYNC200**: User-configured error for blocking sync calls in async functions. Does nothing by default, see [`trio200-blocking-calls`](#trio200-blocking-calls) for how to configure it.
49
-
-**ASYNC210**: Sync HTTP call in async function, use `httpx.AsyncClient`.
46
+
Note: 22X, 23X and 24X has not had asyncio-specific suggestions written.
47
+
-**ASYNC200**: User-configured error for blocking sync calls in async functions. Does nothing by default, see [`async200-blocking-calls`](#async200-blocking-calls) for how to configure it.
48
+
-**ASYNC210**: Sync HTTP call in async function, use `httpx.AsyncClient`. This and the other ASYNC21x checks look for usage of `urllib3` and `httpx.Client`, and recommend using `httpx.AsyncClient` as that's the largest http client supporting anyio/trio.
50
49
-**ASYNC211**: Likely sync HTTP call in async function, use `httpx.AsyncClient`. Looks for `urllib3` method calls on pool objects, but only matching on the method signature and not the object.
51
50
-**ASYNC212**: Blocking sync HTTP call on httpx object, use httpx.AsyncClient.
52
-
-**ASYNC220**: Sync process call in async function, use `await nursery.start(trio.run_process, ...)`.
53
-
-**ASYNC221**: Sync process call in async function, use `await trio.run_process(...)`.
54
-
-**ASYNC222**: Sync `os.*` call in async function, wrap in `await trio.to_thread.run_sync()`.
55
-
-**ASYNC230**: Sync IO call in async function, use `trio.open_file(...)`.
56
-
-**ASYNC231**: Sync IO call in async function, use `trio.wrap_file(...)`.
57
-
-**ASYNC232**: Blocking sync call on file object, wrap the file object in `trio.wrap_file()` to get an async file object.
58
-
-**ASYNC240**: Avoid using `os.path` in async functions, prefer using `trio.Path` objects.
51
+
-**ASYNC220**: Sync process call in async function, use `await nursery.start([trio|anyio].run_process, ...)`.
52
+
-**ASYNC221**: Sync process call in async function, use `await [trio|anyio].run_process(...)`.
53
+
-**ASYNC222**: Sync `os.*` call in async function, wrap in `await [trio|anyio].to_thread.run_sync()`.
54
+
-**ASYNC230**: Sync IO call in async function, use `[trio|anyio].open_file(...)`.
55
+
-**ASYNC231**: Sync IO call in async function, use `[trio|anyio].wrap_file(...)`.
56
+
-**ASYNC232**: Blocking sync call on file object, wrap the file object in `[trio|anyio].wrap_file()` to get an async file object.
57
+
-**ASYNC240**: Avoid using `os.path` in async functions, prefer using `[trio|anyio].Path` objects.
59
58
60
59
### Warnings disabled by default
61
-
-**ASYNC900**: Async generator without `@asynccontextmanager` not allowed.
62
-
-**ASYNC910**: Exit or `return` from async function with no guaranteed checkpoint or exception since function definition.
60
+
-**ASYNC900**: Async generator without `@asynccontextmanager` not allowed. You might want to enable this on a codebase since async generators are inherently unsafe and cleanup logic might not be performed. See https://github.com/python-trio/flake8-async/issues/211 and https://discuss.python.org/t/using-exceptiongroup-at-anthropic-experience-report/20888/6 for discussion.
61
+
-**ASYNC910**: Exit or `return` from async function with no guaranteed checkpoint or exception since function definition. You might want to enable this on a codebase to make it easier to reason about checkpoints, and make the logic of ASYNC911 correct.
63
62
-**ASYNC911**: Exit, `yield` or `return` from async iterable with no guaranteed checkpoint since possible function entry (yield or function definition)
64
63
Checkpoints are `await`, `async for`, and `async with` (on one of enter/exit).
65
64
66
65
### Removed Warnings
66
+
-**TRIOxxx**: All error codes are now renamed ASYNCxxx
67
67
-**TRIO107**: Renamed to TRIO910
68
68
-**TRIO108**: Renamed to TRIO911
69
69
-**TRIO117**: Don't raise or catch `trio.[NonBase]MultiError`, prefer `[exceptiongroup.]BaseExceptionGroup`. `MultiError` was removed in trio==0.24.0.
# catching any one of the exceptions in multi-library files will suppress errors on the bare except. It's unlikely a try block contains code that can raise multiple ones.
0 commit comments