Skip to content

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

Closed
kumaraditya303 opened this issue Feb 9, 2025 · 0 comments
Closed

avoid mixing pure python and C implementation of asyncio #129874

kumaraditya303 opened this issue Feb 9, 2025 · 0 comments
Labels
stdlib Python modules in the Lib dir topic-asyncio

Comments

@kumaraditya303
Copy link
Contributor

kumaraditya303 commented Feb 9, 2025

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 and enter_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

@github-project-automation github-project-automation bot moved this to Todo in asyncio Feb 9, 2025
@picnixz picnixz added the stdlib Python modules in the Lib dir label Feb 9, 2025
@github-project-automation github-project-automation bot moved this from Todo to Done in asyncio Feb 10, 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
Labels
stdlib Python modules in the Lib dir topic-asyncio
Projects
Status: Done
Development

No branches or pull requests

2 participants