-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Recommended way to run background tasks #3459
Comments
aiojobs perfectly handles this problem. |
GitMate.io thinks the contributors most likely able to help are @asvetlov, and @aio-libs-bot. Possibly related issues are #2246 (What's the recommended way of passing information to middlewares), #1104 (Rewrite doc section about background tasks), #3401 (Run background task in master process?), #2375 (add a way to run an app asynchron), and #2745 (Running out of memory ). |
Great, should I update the docs to make mention of this, and remove the current (deprecated) method? |
I don't think that the current method should be removed since it's works out of the box, but it might be good to mention how aiojobs may help there and why it's better. @asvetlov, what do you think about that? |
aiojobs is referenced at the begin of https://docs.aiohttp.org/en/stable/web_advanced.html Deprecated |
Doc is fixed by #3529 |
aiohttp/examples/background_tasks.py
Line 46 in 3a65252
The loop property on the
Application
class is now deprecated (#3374), but the docs still reference adding background tasks to the loop via this property. What is the recommended way to do that now?The text was updated successfully, but these errors were encountered: