U ¯ªh³ã@s¼ddlmZddlmZddlmZddlmZddlm Z ddl m Z ddl m Z ddlmZdd lmZdd lmZd ZGd d „d eƒZddd„Zddd„Zdd„Zdd„Zdd„ZdS)é)ÚRaw)ÚAlbum)Ú ChatAction)ÚMessageDeleted)Ú MessageEdited)Ú MessageRead)Ú NewMessage)Ú UserUpdate)Ú CallbackQuery)Ú InlineQueryz __tl.handlersc@seZdZdZdS)ÚStopPropagationa If this exception is raised in any of the handlers for a given event, it will stop the execution of all other registered event handlers. It can be seen as the ``StopIteration`` in a for loop but for events. Example usage: >>> from telethon import TelegramClient, events >>> client = TelegramClient(...) >>> >>> @client.on(events.NewMessage) ... async def delete(event): ... await event.delete() ... # No other event handler will have a chance to handle this event ... raise StopPropagation ... >>> @client.on(events.NewMessage) ... async def _(event): ... # Will never be reached, because it is the second handler ... pass N)Ú__name__Ú __module__Ú __qualname__Ú__doc__©rrú` variant. Note that this method only registers callbacks as handlers, and does not attach them to any client. This is useful for external modules that don't have access to the client, but still want to define themselves as a handler. Example: >>> from telethon import events >>> @events.register(events.NewMessage) ... async def handler(event): ... ... ... >>> # (somewhere else) ... >>> from telethon import TelegramClient >>> client = TelegramClient(...) >>> client.add_event_handler(handler) Remember that you can use this as a non-decorator through ``register(event)(callback)``. Args: event (`_EventBuilder` | `type`): The event builder class or instance to be used, for instance ``events.NewMessage``. cs&t|tgƒ}| ˆ¡t|t|ƒ|S)N)ÚgetattrÚ_HANDLERS_ATTRIBUTEÚappendÚsetattr)ÚcallbackÚhandlers©ÚeventrrÚ decoratorNs   zregister..decorator)Ú isinstanceÚtyper)rrrrrÚregister+s   rcCsrd}|rt|tƒst|ƒ}t|tgƒ}| ||f¡t|ƒ}|rn|d8}||}|r^t||ƒr<||=|d7}q<|S)a_ Inverse operation of `register` (though not a decorator). Client-less `remove_event_handler ` variant. **Note that this won't remove handlers from the client**, because it simply can't, so you would generally use this before adding the handlers to the client. This method is here for symmetry. You will rarely need to unregister events, since you can simply just not add them to any client. If no event is given, all events for this callback are removed. Returns how many callbacks were removed. ér)rrrrrÚlen)rrÚfoundrÚiZevrrrÚ unregisterWs  r#cCs t|tƒS)zh Returns `True` if the given callback is an event handler (i.e. you used `register` on it). )Úhasattrr©rrrrÚ is_handlerxsr&cCst|tgƒdd…S)zl Returns a list containing the registered event builders inside the specified callback handler. N©rrr%rrrÚlist€sr(cCs t|tdƒS)zP Like ``list`` but returns `None` if the callback was never registered. Nr'r%rrrÚ _get_handlersˆsr))N)N)ÚrawrZalbumrZ chatactionrZmessagedeletedrZ messageeditedrZ messagereadrZ newmessagerZ userupdater Z callbackqueryr Z inlinequeryr rÚ Exceptionr rr#r&r(r)rrrrÚs           , !