-
-
Notifications
You must be signed in to change notification settings - Fork 749
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
Support custom IOLOOPs #2435
base: master
Are you sure you want to change the base?
Support custom IOLOOPs #2435
Conversation
7706714
to
03ec1b0
Compare
32e28d0
to
46078a9
Compare
38ee9b2
to
6c5b1a1
Compare
@@ -70,10 +71,6 @@ def __init__(self, *args: Any, **kwargs: Any) -> None: | |||
|
|||
self.config = Config(**config_kwargs) | |||
|
|||
def init_process(self) -> None: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure why @graingert removed this from here, please make sure its ok :)
6c5b1a1
to
fcb1cbe
Compare
Any updates regarding this? @Kludex |
Hey guys, Thanks :) |
Summary
This is merge of two PR's
Allow passing a custom loop setup function instead of None #2391
Support passing a custom IOLoop setup function in order to support running
uvicorn
in custom ioloop implementation other that the default anduvloop
.For example this feature will allow using this monitored IOLoop inside
uvicorn
applications :)Link to discussions thread - Add support for custom ioloop implementations #2256
use asyncio.run(..., loop_factory) to avoid asyncio.set_event_loop_policy #2130
set_event_loop_policy
will be deprecated in python 3.13 anduvloop.EventLoopPolicy
is deprecated already, this backports and uses the preferredloop_factory
keyword to configureasyncio.run
Checklist