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
As discussed on Gitter, #514 can be resolved without adding this kwarg, by making move_on_after() a generator-based context manager like fail_after(). And I really don't like Trio's solution to the problem.
Things to check first
Feature description
Trio added the
relative_deadline
kwarg toCancelScope
in python-trio/trio#3010 as part of resolving python-trio/trio#2512 (anyio's equivalent issue is #514).Use case
Requesting this mostly to match
Trio
, and because I want to recommend it in flake8-async ASYNC125 constant-absolute-deadline https://flake8-async.readthedocs.io/en/latest/rules.html#async125The text was updated successfully, but these errors were encountered: