Fix telegram API change, returning '404 Not found' #461
Merged
Conversation
…elegramError rather native exception
Member
|
Sweet, thank you! Perhaps it would make sense to add an exception class to |
Contributor
Author
|
Thank you for feedback! :) |
Member
|
Oh yes, raising |
Contributor
Author
|
Ok. I've updated. |
Member
|
Neat! LGTM |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
For bots with incorrect credentials telegram returns
Because of 404 response status http library raises naive NotFound exception, which is not meant to be caught by a request wrapper. As a result test is broken. This patch catches the exception and raises an internal
telegram.TelegramError('Invalid server response')as it was conceived before in test testInvalidSrvResp.P.S. I'm new to python-telegram-bot, so comments are welcome ;)