-
-
Notifications
You must be signed in to change notification settings - Fork 351
Issues: python-trio/trio
Backwards-incompatible changes - SUBSCRIBE TO THIS THREAD if ...
#1
opened Jan 22, 2017 by
njsmith
Open
13
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
Provide a helper to dump the task tree / stack tree
debugging
missing piece
user happiness
#927
opened Feb 13, 2019 by
njsmith
support for windows named pipes
low-level
missing piece
polish
Windows
#824
opened Dec 27, 2018 by
njsmith
trio.ssl handling for Unicode (IDNA) domains is deeply broken
design discussion
#11
opened Jan 22, 2017 by
njsmith
Design: do we need batched accept / accept_nowait?
design discussion
performance
#14
opened Jan 22, 2017 by
njsmith
Debugging / introspection features
debugging
missing piece
user happiness
#15
opened Jan 22, 2017 by
njsmith
4 tasks
Windows: improve usability for low-level IOCP operations
design discussion
low-level
potential API breaker
Windows
#26
opened Jan 22, 2017 by
njsmith
3 tasks
Design: alternative scheduling models
design discussion
performance
#32
opened Jan 23, 2017 by
njsmith
Improve low-level IO monitor functions (for IOCP and kqueue)
low-level
potential API breaker
todo soon
#40
opened Feb 5, 2017 by
njsmith
Make it easier to tell where a Cancelled exception came from
cancellation
debugging
design discussion
user happiness
#44
opened Feb 11, 2017 by
njsmith
Missing feature: sendfile
asyncio feature parity
design discussion
missing piece
polish
#45
opened Feb 11, 2017 by
njsmith
Is our current strategy for handling instrument errors optimal?
design discussion
#47
opened Feb 12, 2017 by
njsmith
Possible API breakers in ParkingLot
design discussion
potential API breaker
#53
opened Feb 13, 2017 by
njsmith
Should our locks (and semaphores, queues, etc.) be fair?
design discussion
performance
potential API breaker
#54
opened Feb 14, 2017 by
njsmith
Backwards-incompatible changes - SUBSCRIBE TO THIS THREAD if you use trio!
design discussion
#1
opened Jan 22, 2017 by
njsmith
Maybe rework run_in_worker_thread API for cancellation handling?
design discussion
potential API breaker
threads
#60
opened Feb 25, 2017 by
njsmith
Python 3.14: test_ki_protection_doesnt_leave_cyclic_garbage fails
#3209
opened Feb 13, 2025 by
musicinmybrain
TCP_NOTSENT_LOWAT umbrella issue
design discussion
performance
polish
#76
opened Mar 10, 2017 by
njsmith
2 tasks
docs: default_role = "obj" leaves function references without their parens
docs
todo soon
#78
opened Mar 10, 2017 by
njsmith
Can we make forgetting an await be an error?
debugging
user happiness
#79
opened Mar 10, 2017 by
njsmith
Should our strategy for handling KeyboardInterrupt be usable for other signals too?
#134
opened Apr 21, 2017 by
njsmith
More ergonomic support for graceful shutdown
cancellation
design discussion
missing piece
#147
opened May 2, 2017 by
merrellb
How should fail_at & fail_after handle MultiErrors?
cancellation
design discussion
exception handling
#59
opened Feb 25, 2017 by
njsmith
Previous Next
ProTip!
Updated in the last three days: updated:>2025-03-05.