-
Notifications
You must be signed in to change notification settings - Fork 6k
shield-update-fetcher #3657
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
shield-update-fetcher #3657
Conversation
# Conflicts: # telegram/ext/_application.py
harshil21
left a comment
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.
Nice. Though can't we just use asyncio.shield() in app.start()?
That is actually way better! Don't know why I didn't think of it :D It works in a manual test. Let's see if the CI is happy as well - I'm not on a linux machine rn … |
This reverts commit 9cbb070.
|
So apparently |
See https://t.me/pythontelegrambotgroup/670240?thread=670177 for a reference.
I'll have to check if I can write a unit test for this special case …
Checklist for PRs
[ ] Added.. versionadded:: version,.. versionchanged:: versionor.. deprecated:: versionto the docstrings for user facing changes (for methods/class descriptions, arguments and attributes)[ ] Added myself alphabetically toAUTHORS.rst(optional)[ ] Added new classes & modules to the docs and all suitable__all__s