Project Name | Stars | Downloads | Repos Using This | Packages Using This | Most Recent Commit | Total Releases | Latest Release | Open Issues | License | Language |
---|---|---|---|---|---|---|---|---|---|---|
Python Telegram Bot | 22,028 | 2,165 | 310 | 4 days ago | 120 | June 28, 2022 | 14 | gpl-3.0 | Python | |
We have made you a wrapper you can't refuse | ||||||||||
Chat | 10,292 | 1 | 2 days ago | 136 | September 06, 2022 | 34 | gpl-3.0 | Go | ||
Instant messaging platform. Backend in Go. Clients: Swift iOS, Java Android, JS webapp, scriptable command line; chatbots | ||||||||||
Node Telegram Bot Api | 7,093 | 1,940 | 283 | 19 days ago | 60 | August 29, 2022 | 70 | mit | JavaScript | |
Telegram Bot API for NodeJS | ||||||||||
Nonebot2 | 4,446 | a day ago | 21 | June 20, 2022 | 5 | mit | Python | |||
跨平台 Python 异步聊天机器人框架 / Asynchronous multi-platform chatbot framework written in Python | ||||||||||
Bottender | 4,044 | 38 | 19 | 2 months ago | 215 | November 10, 2021 | 72 | mit | TypeScript | |
⚡️ A framework for building conversational user interfaces. | ||||||||||
Koishi | 2,815 | 7 | 36 | a day ago | 65 | September 08, 2021 | 38 | mit | TypeScript | |
Cross-platform chatbot framework made with love | ||||||||||
Telegram.bot | 2,678 | 348 | 185 | 4 days ago | 112 | June 16, 2022 | 48 | mit | C# | |
.NET Client for Telegram Bot API | ||||||||||
Telegram Bot Sdk | 2,665 | 250 | 47 | a day ago | 20 | December 10, 2020 | 2 | bsd-3-clause | PHP | |
🤖 Telegram Bot API PHP SDK. Lets you build Telegram Bots easily! Supports Laravel out of the box. | ||||||||||
Messaging Apis | 1,854 | 34 | 14 | 4 months ago | 112 | October 04, 2021 | 11 | mit | TypeScript | |
Messaging APIs for multi-platform | ||||||||||
Claudia Bot Builder | 1,675 | 2 years ago | 11 | mit | JavaScript | |||||
Create chat bots for Facebook Messenger, Slack, Amazon Alexa, Skype, Telegram, Viber, Line, GroupMe, Kik and Twilio and deploy to AWS Lambda in minutes |
We have made you a wrapper you can't refuse
We have a vibrant community of developers helping each other in our Telegram group. Join us!
Stay tuned for library updates and new releases on our Telegram Channel.
This library provides a pure Python, asynchronous interface for the Telegram Bot API. It's compatible with Python versions 3.7+.
In addition to the pure API implementation, this library features a number of high-level classes to
make the development of bots easy and straightforward. These classes are contained in the
telegram.ext
submodule.
A pure API implementation without telegram.ext
is available as the standalone package python-telegram-bot-raw
. See here for details.
Installing both python-telegram-bot
and python-telegram-bot-raw
in conjunction will result in undesired side-effects, so only install one of both.
All types and methods of the Telegram Bot API 6.7 are supported.
You can install or upgrade python-telegram-bot
via
$ pip install python-telegram-bot --upgrade
To install a pre-release, use the --pre
flag in addition.
You can also install python-telegram-bot
from source, though this is usually not necessary.
$ git clone https://github.com/python-telegram-bot/python-telegram-bot
$ cd python-telegram-bot
$ python setup.py install
We sign all the releases with a GPG key.
The signatures are uploaded to both the GitHub releases page and the PyPI project and end with a suffix .asc
.
Please find the public keys here.
The keys are named in the format <first_version>-<last_version>.gpg
or <first_version>-current.gpg
if the key is currently being used for new releases.
In addition, the GitHub release page also contains the sha1 hashes of the release files in the files with the suffix .sha1
.
This allows you to verify that a release file that you downloaded was indeed provided by the python-telegram-bot
team.
python-telegram-bot
tries to use as few 3rd party dependencies as possible.
However, for some features using a 3rd party library is more sane than implementing the functionality again.
As these features are optional, the corresponding 3rd party dependencies are not installed by default.
Instead, they are listed as optional dependencies.
This allows to avoid unnecessary dependency conflicts for users who don't need the optional features.
The only required dependency is httpx ~= 0.24.1 for
telegram.request.HTTPXRequest
, the default networking backend.
python-telegram-bot
is most useful when used along with additional libraries.
To minimize dependency conflicts, we try to be liberal in terms of version requirements on the (optional) dependencies.
On the other hand, we have to ensure stability of python-telegram-bot
, which is why we do apply version bounds.
If you encounter dependency conflicts due to these bounds, feel free to reach out.
PTB can be installed with optional dependencies:
pip install python-telegram-bot[passport]
installs the cryptography>=39.0.1 library. Use this, if you want to use Telegram Passport related functionality.pip install python-telegram-bot[socks]
installs httpx[socks]. Use this, if you want to work behind a Socks5 server.pip install python-telegram-bot[http2]
installs httpx[http2]. Use this, if you want to use HTTP/2.pip install python-telegram-bot[rate-limiter]
installs aiolimiter~=1.1.0. Use this, if you want to use telegram.ext.AIORateLimiter
.pip install python-telegram-bot[webhooks]
installs the tornado~=6.2 library. Use this, if you want to use telegram.ext.Updater.start_webhook
/telegram.ext.Application.run_webhook
.pip install python-telegram-bot[callback-data]
installs the cachetools~=5.3.0 library. Use this, if you want to use arbitrary callback_data.pip install python-telegram-bot[job-queue]
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 the telegram.ext.JobQueue
.To install multiple optional dependencies, separate them by commas, e.g. pip install python-telegram-bot[socks,webhooks]
.
Additionally, two shortcuts are provided:
pip install python-telegram-bot[all]
installs all optional dependencies.pip install python-telegram-bot[ext]
installs all optional dependencies that are related to telegram.ext
, i.e. [rate-limiter, webhooks, callback-data, job-queue]
.Our Wiki contains an Introduction to the API explaining how the pure Bot API can be accessed via python-telegram-bot
.
Moreover, the Tutorial: Your first Bot gives an introduction on how chatbots can be easily programmed with the help of the telegram.ext
module.
python-telegram-bot
.
It contains descriptions of all available classes, modules, methods and arguments as well as the changelog.python-telegram-bot
and other useful resources that go beyond the technical documentation.python-telegram-bot
.
Even if it is not your approach for learning, please take a look at echobot.py
. It is the de facto base for most of the bots out there.
The code for these examples is released to the public domain, so you can start by grabbing the code and building on top of it.If the resources mentioned above don't answer your questions or simply overwhelm you, there are several ways of getting help.
Since v20.0, python-telegram-bot
is built on top of Pythons asyncio
module.
Because asyncio
is in general single-threaded, python-telegram-bot
does currently not aim to be thread-safe.
Noteworthy parts of python-telegram-bots
API that are likely to cause issues (e.g. race conditions) when used in a multi-threaded setting include:
telegram.ext.Application/Updater.update_queue
telegram.ext.ConversationHandler.check/handle_update
telegram.ext.CallbackDataCache
telegram.ext.BasePersistence
telegram.ext.filters
module that allow to add/remove allowed users/chats at runtimeContributions of all sizes are welcome. Please review our contribution guidelines to get started. You can also help by reporting bugs or feature requests.
Occasionally we are asked if we accept donations to support the development. While we appreciate the thought, maintaining PTB is our hobby, and we have almost no running costs for it. We therefore have nothing set up to accept donations. If you still want to donate, we kindly ask you to donate to another open source project/initiative of your choice instead.
You may copy, distribute and modify the software provided that modifications are described and licensed for free under LGPL-3. Derivatives works (including modifications or anything statically linked to the library) can only be redistributed under LGPL-3, but applications that use the library don't have to be.