telegram.ext.ConversationHandler¶
-
class
telegram.ext.
ConversationHandler
(entry_points, states, fallbacks, allow_reentry=False, per_chat=True, per_user=True, per_message=False, conversation_timeout=None, name=None, persistent=False)¶ Bases:
telegram.ext.handler.Handler
A handler to hold a conversation with a single user by managing four collections of other handlers. Note that neither posts in Telegram Channels, nor group interactions with multiple users are managed by instances of this class.
The first collection, a
list
namedentry_points
, is used to initiate the conversation, for example with atelegram.ext.CommandHandler
ortelegram.ext.RegexHandler
.The second collection, a
dict
namedstates
, contains the different conversation steps and one or more associated handlers that should be used if the user sends a message when the conversation with them is currently in that state. Here you can also define a state forTIMEOUT
to define the behavior whenconversation_timeout
is exceeded, and a state forWAITING
to define behavior when a new update is received while the previous@run_async
decorated handler is not finished.The third collection, a
list
namedfallbacks
, is used if the user is currently in a conversation but the state has either no associated handler or the handler that is associated to the state is inappropriate for the update, for example if the update contains a command, but a regular text message is expected. You could use this for a/cancel
command or to let the user know their message was not recognized.The fourth, optional collection of handlers, a
list
namedtimed_out_behavior
is used if the wait forrun_async
takes longer than defined inrun_async_timeout
. For example, you can let the user know that they should wait for a bit before they can continue.To change the state of conversation, the callback function of a handler must return the new state after responding to the user. If it does not return anything (returning
None
by default), the state will not change. If an entry point callback function returns None, the conversation ends immediately after the execution of this callback function. To end the conversation, the callback function must returnEND
or-1
. To handle the conversation timeout, use handlerTIMEOUT
or-2
.-
entry_points
¶ A list of
Handler
objects that can trigger the start of the conversation.Type: List[ telegram.ext.Handler
]
-
states
¶ A
dict
that defines the different states of conversation a user can be in and one or more associatedHandler
objects that should be used in that state.Type: Dict[ object
, List[telegram.ext.Handler
]]
-
fallbacks
¶ A list of handlers that might be used if the user is in a conversation, but every handler for their current state returned
False
oncheck_update
.Type: List[ telegram.ext.Handler
]
-
allow_reentry
¶ Determines if a user can restart a conversation with an entry point.
Type: bool
-
per_chat
¶ If the conversationkey should contain the Chat’s ID.
Type: bool
-
per_user
¶ If the conversationkey should contain the User’s ID.
Type: bool
-
per_message
¶ If the conversationkey should contain the Message’s ID.
Type: bool
-
conversation_timeout
¶ Optional. When this handler is inactive more than this timeout (in seconds), it will be automatically ended. If this value is 0 (default), there will be no timeout. when it’s triggered. The last received update will be handled by ALL the handler’s who’s check_update method returns True that are in the state
ConversationHandler.TIMEOUT
.Type: float`|:obj:`datetime.timedelta
-
name
¶ Optional. The name for this conversationhandler. Required for persistence
Type: str
-
persistent
¶ Optional. If the conversations dict for this handler should be saved. Name is required and persistence has to be set in
telegram.ext.Updater
Type: bool
Parameters: - entry_points (List[
telegram.ext.Handler
]) – A list ofHandler
objects that can trigger the start of the conversation. The first handler whichcheck_update
method returnsTrue
will be used. If all returnFalse
, the update is not handled. - states (Dict[
object
, List[telegram.ext.Handler
]]) – Adict
that defines the different states of conversation a user can be in and one or more associatedHandler
objects that should be used in that state. The first handler whichcheck_update
method returnsTrue
will be used. - fallbacks (List[
telegram.ext.Handler
]) – A list of handlers that might be used if the user is in a conversation, but every handler for their current state returnedFalse
oncheck_update
. The first handler whichcheck_update
method returnsTrue
will be used. If all returnFalse
, the update is not handled. - allow_reentry (
bool
, optional) – If set toTrue
, a user that is currently in a conversation can restart the conversation by triggering one of the entry points. - per_chat (
bool
, optional) – If the conversationkey should contain the Chat’s ID. Default isTrue
. - per_user (
bool
, optional) – If the conversationkey should contain the User’s ID. Default isTrue
. - per_message (
bool
, optional) – If the conversationkey should contain the Message’s ID. Default isFalse
. - conversation_timeout (
float
|datetime.timedelta
, optional) – When this handler is inactive more than this timeout (in seconds), it will be automatically ended. If this value is 0 or None (default), there will be no timeout. The last received update will be handled by ALL the handler’s who’s check_update method returns True that are in the stateConversationHandler.TIMEOUT
. - name (
str
, optional) – The name for this conversationhandler. Required for persistence - persistent (
bool
, optional) – If the conversations dict for this handler should be saved. Name is required and persistence has to be set intelegram.ext.Updater
Raises: ValueError
-
END
= -1¶ Used as a constant to return when a conversation is ended.
Type: int
-
TIMEOUT
= -2¶ Used as a constant to handle state when a conversation is timed out.
Type: int
-
WAITING
= -3¶ Used as a constant to handle state when a conversation is still waiting on the previous
@run_sync
decorated running handler to finish.Type: int
-
check_update
(update)¶ Determines whether an update should be handled by this conversationhandler, and if so in which state the conversation currently is.
Parameters: update ( telegram.Update
) – Incoming telegram update.Returns: bool
-
handle_update
(update, dispatcher, check_result, context=None)¶ Send the update to the callback for the current state and Handler
Parameters: - check_result – The result from check_update. For this handler it’s a tuple of key, handler, and the handler’s check result.
- update (
telegram.Update
) – Incoming telegram update. - dispatcher (
telegram.ext.Dispatcher
) – Dispatcher that originated the Update.
-
persistence
= None¶ The persistence used to store conversations. Set by dispatcher
Type: telegram.ext.BasePersistance
-