S"j#ddlZddlZddlZddlmZmZmZddlmZm Z ddl m Z m Z m Z ddlmZeGdd eZy) N) EventBuilder EventCommonname_inner_event)utilshelpers)types functionscustom) SenderGettercdeZdZdZ d ddddfd Zed dZfdZGdd ee Z xZ S) InlineQuerya Occurs whenever you sign in as a bot and a user sends an inline query such as ``@bot query``. Args: users (`entity`, optional): May be one or more entities (username/peer/etc.), preferably IDs. By default, only inline queries from these users will be handled. blacklist_users (`bool`, optional): Whether to treat the users as a blacklist instead of as a whitelist (default). This means that every chat will be handled *except* those specified in ``users`` which will be ignored if ``blacklist_users=True``. pattern (`str`, `callable`, `Pattern`, optional): If set, only queries matching this pattern will be handled. You can specify a regex-like string which will be matched against the message, a callable function that returns `True` if a message is acceptable, or a compiled regex pattern. Example .. code-block:: python from telethon import events @client.on(events.InlineQuery) async def handler(event): builder = event.builder # Two options (convert user text to UPPERCASE or lowercase) await event.answer([ builder.article('UPPERCASE', text=event.text.upper()), builder.article('lowercase', text=event.text.lower()), ]) NF)blacklist_usersfuncpatternc8t||||t|tr%t j |j |_y|r t|r||_yt|dr't|j r|j |_ytd)N)blacklist_chatsrmatchzInvalid pattern type given) super__init__ isinstancestrrecompilerrcallablehasattr TypeError)selfusersrrr __class__s \/var/www/api.ozpay.ru/ozpay/venv/lib/python3.12/site-packages/telethon/events/inlinequery.pyrzInlineQuery.__init__2st dK gs #::g.44DLHW-"DL Wg &8GMM+B"==DL89 9cZt|tjr|j|SyN)rr UpdateBotInlineQueryEvent)clsupdateothersself_ids r"buildzInlineQuery.build?s& fe88 999V$ $ :r#c|jr%|j|j}|sy||_t||Sr%)rtext pattern_matchrfilter)reventrr!s r"r0zInlineQuery.filterDs9 <<LL,E"'E w~e$$r#ceZdZdZfdZfdZedZedZedZ edZ edZ dd d d d d d d Z e dZxZS)InlineQuery.Eventa  Represents the event of a new callback query. Members: query (:tl:`UpdateBotInlineQuery`): The original :tl:`UpdateBotInlineQuery`. Make sure to access the `text` property of the query if you want the text rather than the actual query object. pattern_match (`obj`, optional): The resulting object from calling the passed ``pattern`` function, which is ``re.compile(...).match`` by default. ct|tj|jt j||j||_d|_d|_y)N) chat_peerF) rrr PeerUseruser_idr queryr/ _answered)rr8r!s r"rzInlineQuery.Event.__init__\sJ G u~~emm'D  E  ! !$ 6DJ!%D "DNr#ct||tj|j|j |j \|_|_yr%) r _set_clientr_get_entity_pair sender_id _entities_mb_entity_cache_sender _input_sender)rclientr!s r"r;zInlineQuery.Event._set_clientcs@ G  '/4/E/E0G0G0I ,DL$,r#c.|jjS)zI Returns the unique identifier for the query ID. )r8query_idrs r"idzInlineQuery.Event.idhs ::&& &r#c.|jjS)zR Returns the text the user used to make the inline query. )r8rEs r"r.zInlineQuery.Event.textos ::## #r#c.|jjS)z The string the user's client used as an offset for the query. This will either be empty or equal to offsets passed to `answer`. )r8offsetrEs r"rIzInlineQuery.Event.offsetvs ::$$ $r#c.|jjS)z If the user location is requested when using inline mode and the user's device is able to send it, this will return the :tl:`GeoPoint` with the position of the user. )r8georEs r"rKzInlineQuery.Event.geo~s::>> !r#c@tj|jS)z~ Returns a new `InlineBuilder ` instance. )r InlineBuilder_clientrEs r"builderzInlineQuery.Event.builders '' 5 5r#NF)gallery next_offsetprivate switch_pmswitch_pm_paramc K|jry|rY|Dcgc]}|j|} }tj| d{| Dcgc]}|j }}ng}|rt j ||}|jtjj|jj||||||d{Scc}w7cc}w7w)a Answers the inline query with the given results. See the documentation for `builder` to know what kind of answers can be given. Args: results (`list`, optional): A list of :tl:`InputBotInlineResult` to use. You should use `builder` to create these: .. code-block:: python builder = inline.builder r1 = builder.article('Be nice', text='Have a nice day') r2 = builder.article('Be bad', text="I don't like you") await inline.answer([r1, r2]) You can send up to 50 results as documented in https://core.telegram.org/bots/api#answerinlinequery. Sending more will raise ``ResultsTooMuchError``, and you should consider using `next_offset` to paginate them. cache_time (`int`, optional): For how long this result should be cached on the user's client. Defaults to 0 for no cache. gallery (`bool`, optional): Whether the results should show as a gallery (grid) or not. next_offset (`str`, optional): The offset the client will send when the user scrolls the results and it repeats the request. private (`bool`, optional): Whether the results should be cached by Telegram (not private) or by the user's client (private). switch_pm (`str`, optional): If set, this text will be shown in the results to allow the user to switch to private messages. switch_pm_param (`str`, optional): Optional parameter to start the bot with if `switch_pm` was used. Example: .. code-block:: python @bot.on(events.InlineQuery) async def handler(event): builder = event.builder rev_text = event.text[::-1] await event.answer([ builder.article('Reverse text', text=rev_text), builder.photo('/path/to/photo.jpg') ]) N)rDresults cache_timerQrRrSrT) r9 _as_futureasynciowaitresultr InlineBotSwitchPMrNr messagesSetInlineBotResultsRequestr8rD) rrWrXrQrRrSrTrUxfuturess r"answerzInlineQuery.Event.answersB~~7>?!4??1-??ll7+++077!188:77!33IO ""==!ZZ00#)# +#'>   !@+8 s:C$CC$C C$C(A)C$C" C$C$ctj|rtj|St j j }|j||Sr%)inspect isawaitablerZ ensure_futurer get_running_loop create_future set_result)objfs r"rYzInlineQuery.Event._as_futuresI""3',,S11((*88:A LL Hr#)Nr)__name__ __module__ __qualname____doc__rr;propertyrFr.rIrKrOrb staticmethodrY __classcell__r!s@r"r'r3Ms  # I  '  '  $  $  %  %  "  "  6  601_ 4_ B    r#r'r%)NN) rlrmrnror classmethodr,r0rr r'rrrss@r"rr sN#J :16T4 :%%%j \jjr#r)rdrrZcommonrrrrPrr tlr r r tl.custom.sendergetterr rr#r"rys> ??))1j,jjr#