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

Expose something like gevent.threadpool.ThreadResult? #1742

Open
jamadden opened this issue Jan 12, 2021 · 1 comment
Open

Expose something like gevent.threadpool.ThreadResult? #1742

jamadden opened this issue Jan 12, 2021 · 1 comment
Labels
Type: Enhancement We can do better through adding this

Comments

@jamadden
Copy link
Member

There may be a need, based on #1739.

The changes to AsyncResult that fix the hang in #1739 actually come close, but it's not a thread-safe object either. I don't desire to make it fully thread-safe unless we can guarantee extremely low-overhead for its intended use case.

@jamadden jamadden added the Type: Enhancement We can do better through adding this label Jan 12, 2021
@jamadden
Copy link
Member Author

Another useful primitive might be a thread-safe way to schedule a callback in another thread's hub. (I feel like that's come up before…) That's very primitive, though, given the limitations on callbacks in this context (no blocking API, musn't raise exceptions, etc), so it's possibly only useful for gevent internals.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Enhancement We can do better through adding this
Projects
None yet
Development

No branches or pull requests

1 participant