Constrain python-telegram-bot version to 13.x to sidestep api changes #11
Conversation
This file contains 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
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.
Hi, thanks for this awesome project!
The constraint
python-telegram-bot>=13.0inrequirements.txtcurrently resolves to20.xin the docker container environment, which it seems introduced some breaking changes (can no longer dofrom telegram.ext import Dispatcher).I propose to change the constraint to
python-telegram-bot~=13.0, which resolves to version13.15in the docker container environment. I haven't run all the tests with that version, but it seems to work and that is probably the version people have been using for a while.