Issues: python-trio/trio
Backwards-incompatible changes - SUBSCRIBE TO THIS THREAD if ...
#1
opened Jan 22, 2017 by
njsmith
Open
10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Cancellation may not always immediately happen at checkpoints
cancellation
design discussion
docs
#2973
opened Mar 14, 2024 by
arthur-tacca
Could this lib I made be added to the Awesome Libraries page?
#2963
opened Feb 26, 2024 by
obnoxiousish
When bumping sphinx, remove FrameType workaround in docs/source/conf.py
#2921
opened Jan 10, 2024 by
jakkdl
TaskStatus.started() being a no-op if cancelled can cause deadlocks
#2895
opened Dec 1, 2023 by
oremanj
trio.TrioInternalError when sync func run with trio.to_thread.run_sync returns
#2878
opened Nov 14, 2023 by
jpatel624
Create a Limiter Protocol
typing
Adding static types to trio's interface
#2824
opened Oct 19, 2023 by
jakkdl
Add an
@trio.not_in_async_task
decorator, to error instead of stalling
#2757
opened Aug 17, 2023 by
Zac-HD
Previous Next
ProTip!
Type g p on any issue or pull request to go back to the pull request listing page.