Skip to content

asgiref.sync trio support #509

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

Draft
wants to merge 11 commits into
base: main
Choose a base branch
from

Conversation

graingert
Copy link
Contributor

@graingert graingert commented Apr 12, 2025

this is just a sketch, I've not even tested it on trio yet - just a demo to see approximately how much code needs to change. Ok I needed to try it out so I ported the relevant parts of the suite to anyio

The design I've gone with is to make as few changes to the asyncio "trio not installed" code path as possible, rather than say using anyio and refactoring everything to use a trionic style. I want this to be as minimal and nonintrusive on existing asyncio use cases.

What needs doing is duplicating the test suite with pytest-trio (or using anyio's pytest plugin for both) and fixing the mypy errors. Done!

To fix the mypy errors I'll probably want to move the trio versions of the all the util functions into their own private module Done!

@carltongibson carltongibson marked this pull request as draft April 12, 2025 07:58
@graingert graingert force-pushed the trio-support-in-sync branch from 838227e to 152d990 Compare April 13, 2025 11:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant