-
-
Notifications
You must be signed in to change notification settings - Fork 32k
avoid mixing pure python and C implementation of asyncio #129874
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
Labels
Comments
kumaraditya303
added a commit
that referenced
this issue
Feb 9, 2025
kumaraditya303
added a commit
that referenced
this issue
Feb 9, 2025
This was referenced Feb 9, 2025
kumaraditya303
added a commit
that referenced
this issue
Feb 9, 2025
kumaraditya303
added a commit
that referenced
this issue
Feb 9, 2025
This was referenced Feb 24, 2025
kumaraditya303
added a commit
that referenced
this issue
Feb 24, 2025
kumaraditya303
added a commit
that referenced
this issue
Feb 24, 2025
seehwan
pushed a commit
to seehwan/cpython
that referenced
this issue
Apr 16, 2025
seehwan
pushed a commit
to seehwan/cpython
that referenced
this issue
Apr 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Currently writing tests in asyncio is difficult because we have two separate implementations. The C implementation overrides the pure Python implementation at runtime as such testing python implementation is tricky. I propose that the pure python implementation should use the pure python versions of things like
register_task
andenter_task
so that the it gets tested properly and it makes debugging easier. There should not really be a case where we mix both the implementations, both should be separate.Linked PRs
The text was updated successfully, but these errors were encountered: