Telegram: Don't rely on constants#4016
Merged
gazpachoking merged 1 commit intoFlexget:developfrom Jul 17, 2024
Merged
Conversation
BrutuZ
added a commit
to BrutuZ/Flexget
that referenced
this pull request
Jul 22, 2024
gazpachoking
added a commit
that referenced
this pull request
Aug 4, 2024
[fix] Telegram: Fix behavior change from #4016
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Motivation for changes:
Flexget started to crash after loosening the allowed
python-telegram-botversionsDetailed changes:
parse_modedirectly instead of reading from the dependency as newer versions store the constant on a separate module.Addressed issues/feature requests:
Config usage if relevant (new plugin or updated schema):