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.

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

Jump to bottom

Use AnyIO (optionally) #506

Open
madkote opened this issue Feb 21, 2023 · 2 comments
Open

Use AnyIO (optionally) #506

madkote opened this issue Feb 21, 2023 · 2 comments

Comments

@madkote
Copy link

madkote commented Feb 21, 2023

Currently ThreadPoolExecutor is in use. It would be nice to have an option to use AnyIO.

Why:

  • If a project is using AnyIO, janus uses ThreadPoolExecutor and there are a lot of worker threads for janus only hanging around.
madkote added a commit to madkote/janus that referenced this issue Feb 21, 2023
@madkote
aio-libs#506 anyio integration - initial
af937a3
@madkote
Copy link
Author

madkote commented Feb 21, 2023

open to discuss about details

@x42005e1f x42005e1f mentioned this issue Oct 26, 2024
Open
@x42005e1f
Copy link

You can use Culsans if you need AnyIO support. It does not have strong dependencies on AsyncIO, so it fully supports Trio. It's not fully compatible with Janus due to replacing close() with shutdown(), but it's fully compatible with Python 3.13 queues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@madkote @x42005e1f