From 582d8859acd5b98353739efb59b5f738db589423 Mon Sep 17 00:00:00 2001 From: apepenkov <39992738+apepenkov@users.noreply.github.com> Date: Fri, 10 Nov 2023 09:18:36 +0300 Subject: [PATCH] Improve documentation for Message Co-authored-by: Lonami --- client/src/telethon/_impl/client/types/message.py | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/client/src/telethon/_impl/client/types/message.py b/client/src/telethon/_impl/client/types/message.py index d672c1bc..05adbaed 100644 --- a/client/src/telethon/_impl/client/types/message.py +++ b/client/src/telethon/_impl/client/types/message.py @@ -46,7 +46,15 @@ class Message(metaclass=NoPublicConstructor): You can get a message from :class:`telethon.events.NewMessage`, or from methods such as :meth:`telethon.Client.get_messages`. - If the message is empty (like when it's not found using :meth:`telethon.Client.get_messages_with_ids`), + Empty messages can occur very rarely when fetching the message history. + In these cases, only the :attr:`id` and :attr`peer` properties are guaranteed to be present. + To determine whether a message is empty, its truthy value can be checked via :meth:`object.__bool__`: + + .. code-block:: python + + async for message in client.iter_messages(chat): + if not message: + print('Found empty message with ID', message.id) its ``__bool__`` method will yield :data:`False`. """