Skip to content
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

Make WSGI implementation agnostic to async library #845

Closed

Conversation

florimondmanca
Copy link
Member

Builds on #844

Last part of stage 1 of #169 (comment): rework WSGIMiddleware so that it calls into AsyncBackend rather than asyncio directly.

This is the gnarliest of refactor PRs, since this component does some close concurrency. I know the backend.call_soon() method won't stay here when trio is added (trio doesn't have such a "schedule a callback from outside the event loop" API), and we'll need to refactor this, but for now the goal is to have some abstraction without changing too much the implementation logic. Tests pass locally, so I'm happy (but let's see what CI says).

@florimondmanca
Copy link
Member Author

Closing for now, see #842 (comment)

@florimondmanca florimondmanca deleted the fm/asyncio-agnostic-wsgi branch November 8, 2020 20:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant