Let’s start the quick references section with some useful tips to keep in mind, with the hope that you will understand why certain things work the way that they do.
- Code without errors doesn’t work
- How can I except FloodWaitError?
- My account was deleted/limited when using the library
- How can I use a proxy?
- How do I access a field?
- AttributeError: ‘coroutine’ object has no attribute ‘id’
- sqlite3.OperationalError: database is locked
- event.chat or event.sender is None
- What does “bases ChatGetter” mean?
- Can I use Flask with the library?
- Can I use Anaconda/Spyder/IPython with the library?
Then it probably has errors, but you haven’t enabled logging yet. To enable logging, at the following code to the top of your main file:
import logging logging.basicConfig(format='[%(levelname) 5s/%(asctime)s] %(name)s: %(message)s', level=logging.WARNING)
You can change the logging level to be something different, from less to more information:
level=logging.CRITICAL # won't show errors (same as disabled) level=logging.ERROR # will only show errors that you didn't handle level=logging.WARNING # will also show messages with medium severity, such as internal Telegram issues level=logging.INFO # will also show informational messages, such as connection or disconnections level=logging.DEBUG # will show a lot of output to help debugging issues in the library
See the official Python documentation for more information on logging.
You can use all errors from the API by importing:
from telethon import errors
And except them as such:
try: await client.send_message(chat, 'Hi') except errors.FloodWaitError as e: # e.seconds is how many seconds you have # to wait before making the request again. print('Flood for', e.seconds)
The library will only do things that you tell it to do. If you use the library with bad intentions, Telegram will hopefully ban you.
However, you may also be part of a limited country, such as Iran or Russia. In that case, we have bad news for you. Telegram is much more likely to ban these numbers, as they are often used to spam other accounts, likely through the use of libraries like this one. The best advice we can give you is to not abuse the API, like calling many requests really quickly, and to sign up with these phones through an official application.
We have also had reports from Kazakhstan and China, where connecting would fail. To solve these connection problems, you should use a proxy.
Telegram may also ban virtual (VoIP) phone numbers, as again, they’re likely to be used for spam.
If you want to check if your account has been limited,
simply send a private message to @SpamBot through Telegram itself.
You should notice this by getting errors like
which means you’re limited, for instance,
when sending a message to some accounts but not others.
For more discussion, please see issue 297.
This is basic Python knowledge. You should use the dot operator:
me = await client.get_me() print(me.username) # ^ we used the dot operator to access the username attribute result = await client(functions.photos.GetUserPhotosRequest( user_id='me', offset=0, max_id=0, limit=100 )) # Working with list is also pretty basic print(result.photos.sizes[-1].type) # ^ ^ ^ ^ ^ # | | | | \ type # | | | \ last size # | | \ list of sizes # access | \ first photo from the list # the... \ list of photos # # To print all, you could do (or mix-and-match): for photo in result.photos: for size in photo.sizes: print(size.type)
You either forgot to:
import telethon.sync # ^^^^^ import sync
async def handler(event): me = await client.get_me() # ^^^^^ note the await print(me.username)
An older process is still running and is using the same
This error occurs when two or more clients use the same session, that is, when you write the same session name to be used in the client:
- You have an older process using the same session file.
- You have two different scripts running (interactive sessions count too).
- You have two clients in the same script running at the same time.
The solution is, if you need two clients, use two sessions. If the
problem persists and you’re on Linux, you can use
to find out the process locking the file. As a last resort, you can
reboot your system.
If you really dislike SQLite, use a different session storage. There is an entire section covering that at Session Files.
Telegram doesn’t always send this information in order to save bandwidth. If you need the information, you should fetch it yourself, since the library won’t do unnecessary work unless you need to:
async def handler(event): chat = await event.get_chat() sender = await event.get_sender()
In Python, classes can base others. This is called inheritance. What it means is that “if a class bases another, you can use the other’s methods too”.
So if you have a message, you can access that too:
# ChatGetter has a chat_id property, and Message bases ChatGetter. # Thus you can use ChatGetter properties and methods from Message print(message.chat_id)
Telegram has a lot to offer, and inheritance helps the library reduce boilerplate, so it’s important to know this concept. For newcomers, this may be a problem, so we explain what it means here in the FAQ.
Yes, if you know what you are doing. However, you will probably have a lot of headaches to get threads and asyncio to work together. Instead, consider using Quart, an asyncio-based alternative to Flask.
Check out quart_login.py for an example web-application based on Quart.
Yes, but these interpreters run the asyncio event loop implicitly,
which interferes with the
telethon.sync magic module.
If you use them, you should not import
# Change any of these...: from telethon import TelegramClient, sync, ... from telethon.sync import TelegramClient, ... # ...with this: from telethon import TelegramClient, ...
You are also more likely to get “sqlite3.OperationalError: database is locked”
with them. If they cause too much trouble, just write your code in a
file and run that, or use the normal