Skip to content

Issues: python-trio/outcome

Beta
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.

Sign up for GitHub

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

Clear current search query, filters, and sorts
0 Open 11 Closed
0 Open 11 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

switch default branch to main
#46 by graingert was closed Mar 28, 2025
2
Make a new release
#37 by jakkdl was closed Oct 17, 2023
8
Next release
#22 by RazerM was closed Sep 11, 2018
Unintuitive inheritance in Python 3.5+
#17 by nonsleepr was closed Jul 5, 2018
@RazerM
outcome has a test dependency on trio, while trio has a regular dependency on outcome
#12 by catern was closed Sep 4, 2018
7
Monadic behavior
#10 by bluetech was closed Apr 15, 2018
2
Use introspection to combine capture and acapture
#9 by bluetech was closed Apr 15, 2018
1
Wrap a function to return Outcome
#8 by bluetech was closed Apr 17, 2018
2
Should Outcome objects consume themselves when unwrapped?
#7 by RazerM was closed Apr 18, 2018
1
Support **kwargs in capture/acapture?
#5 by njsmith was closed Apr 11, 2018
1
MacOS CI broken
#2 by njsmith was closed Mar 28, 2018
3
ProTip! Exclude everything labeled bug with -label:bug.