pip install python-telegram-bot.Īdditionally, two shortcuts are provided: To install multiple optional dependencies, separate them by commas, e.g. pip install python-telegram-bot installs the APScheduler~=3.10.1 library and enforces pytz>=2018.6, where pytz is a dependency of APScheduler.Use this, if you want to use arbitrary callback_data. pip install python-telegram-bot installs the cachetools~=5.3.1 library.Use this, if you want to use _webhook/ _webhook. pip install python-telegram-bot installs the tornado~=6.2 library.pip install python-telegram-bot installs aiolimiter~=1.1.0.pip install python-telegram-bot installs httpx.Use this, if you want to work behind a Socks5 server. Use this, if you want to use Telegram Passport related functionality. pip install python-telegram-bot installs the cryptography>=39.0.1 library.PTB can be installed with optional dependencies:
If you encounter dependency conflicts due to these bounds, feel free to reach out. On the other hand, we have to ensure stability of python-telegram-bot, which is why we do apply version bounds. To minimize dependency conflicts, we try to be liberal in terms of version requirements on the (optional) dependencies. Python-telegram-bot is most useful when used along with additional libraries. The only required dependency is httpx ~= 0.24.1 for This allows to avoid unnecessary dependency conflicts for users who don't need the optional features. Instead, they are listed as optional dependencies. However, for some features using a 3rd party library is more sane than implementing the functionality again.Īs these features are optional, the corresponding 3rd party dependencies are not installed by default. Python-telegram-bot tries to use as few 3rd party dependencies as possible. This allows you to verify that a release file that you downloaded was indeed provided by the python-telegram-bot team. In addition, the GitHub release page also contains the sha1 hashes of the release files in the files with the suffix. The keys are named in the format -.gpg or -current.gpg if the key is currently being used for new releases. The signatures are uploaded to both the GitHub releases page and the PyPI project and end with a suffix. $ python setup.py install Verifying Releases
0 kommentar(er)
