You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Listeners: Listeners are a new way to handle incoming user updates (messages, callbacks, etc.). They are more flexible, faster, and easier to use than handlers.
Filters: Filters are now objects that can be combined using logical operators. They are more powerful and flexible than the previous filter system.
Handlers: Now you can register handlers with decorators without the need to use the add_handler method.
FlowCompletion: A new method .get_media(types.Image, key="img") allows you to construct a media object and perform actions like .download() on it.
FlowRequest: Decrypt media directly from FlowRequest using .decrypt_media(key, index).
Client: The client can run without a token but won’t allow API operations (only webhook listening).
SentMessage: The SentMessage object returned by send_message, send_image, etc., contains the message ID and allows to act on the sent message with methods like reply_x, wait_for_x etc.
Flows: Create conditionals for If by using python's operators like ==, !=, >, <, >=, <= etc.
Breaking changes
Async Separation: In the sync version of pywa, no async callbacks or filters are allowed.
Returning SentMessage Object: Functions like send_message, send_image, etc., no longer return a string (message ID). Instead, they return a SentMessage object, which contains the ID and allows further actions.
Filter System Redesign: Filters are now objects rather than simple callables. You can combine filters using logical operators like &, |, and ~.
Reordered Init Parameters: The order of the parameters in the WhatsApp class has been changed and some parameters have been removed.
Handler Factory Changes: Factories in handlers are now limited to CallbackData subclasses (not any callable). Only one class is allowed, not multiple.
Removal of Deprecated Arguments: Deprecated arguments like keyboard (use buttons instead) and body (use caption) have been removed from send_message, send_image, send_video, and send_document.
Server: The function signature webhook_update_handler that used to pass updates manually to the server has been changed.
Deprecated Argument Removal: Deprecated arguments such as keyboard and body have been removed.
Client: The continue_handling param is now set to False by default. so if update is handled, it will not be passed to the next handler unless you set it to True or call update.continue_handling() in the handler.
Flows: The .data_key and .from_ref of the flowjson components renamed to .ref.
Migration steps
If you are using the sync version of pywa, and you have async callbacks or filters, you need to remove them or switch to the async version:
# Old codefrompywaimportWhatsApp, typeswa=WhatsApp(...)
@wa.on_messageasyncdefon_message(_: WhatsApp, msg: types.Message):
msg.reply("Hello, World!")
# New codefrompywa_asyncimportWhatsApp, typeswa=WhatsApp(...)
@wa.on_messageasyncdefon_message(_: WhatsApp, msg: types.Message):
awaitmsg.reply("Hello, World!")
If you use the message ID returned by functions like send_message, send_image, etc (e.g to store it in a database), you need to update your code to use the .id attribute of the SentMessage object:
# Old codemessage_id=wa.send_message("Hello, World!")
db.store_message_id(message_id)
# New codesent_message=wa.send_message("Hello, World!")
db.store_message_id(sent_message.id)
If you are using filters, you need to update your code to use the new filter system:
If you are using lots of handlers, you may want to switch to listeners:
# Old codefrompywaimportWhatsApp, types, filters@wa.on_message(filters.command("start"))defon_start(_: WhatsApp, m: types.Message):
m.reply("How old are you?")
@wa.on_message(filters.text&filters.new(lambda_, m: m.text.isdigit()))defon_age(_: WhatsApp, m: types.Message):
m.reply(f"You are {m.text} years old")
m.reply("What is your name?")
@wa.on_message(filters.text&filters.new(lambda_, m: m.text.isalpha()))defon_name(_: WhatsApp, m: types.Message):
m.reply(f"Hello {m.text}")
# New codefrompywaimportWhatsApp, types, filterswa=WhatsApp(...)
@wa.on_message(filters.command("start"))defon_start(_: WhatsApp, m: types.Message):
age=m.reply("How old are you?").wait_for_reply(
filters=filters.text&filters.new(lambda_, m: m.text.isdigit()),
)
m.reply(f"You are {age.text} years old")
name=m.reply("What is your name?").wait_for_reply(
filters=filters.text&filters.new(lambda_, m: m.text.isalpha()),
)
m.reply(f"Hello {name.text}")
If You are writing the handlers in separate modules and then using add_handler to register the callback wrapped with handler objects, you can now use decorators to register handlers:
# Old code# module1.pyfrompywaimportWhatsApp, typesdefon_start(_: WhatsApp, m: types.Message):
m.reply("How old are you?")
defon_age(_: WhatsApp, m: types.Message):
m.reply(f"You are {m.text} years old")
m.reply("What is your name?")
# module2.pyfrompywaimportWhatsApp, handlers, filterswa=WhatsApp(...)
wa.add_handlers(handlers.MessageHandler(on_start, filters.command("start")))
wa.add_handlers(handlers.MessageHandler(on_age, filters.text&filters.new(lambda_, m: m.text.isdigit())))
# New code# module1.pyfrompywaimportWhatsApp, types, filters@WhatsApp.on_message(filters.command("start")) # we using the class here, not the instance!defon_start(_: WhatsApp, m: types.Message):
m.reply("How old are you?")
@WhatsApp.on_message(filters.text&filters.new(lambda_, m: m.text.isdigit()))defon_age(_: WhatsApp, m: types.Message):
m.reply(f"You are {m.text} years old")
m.reply("What is your name?")
# module2.pyfrompywaimportWhatsAppfrom . importmodule1wa=WhatsApp(..., handlers_modules=[module1])
If you want to keep the continuation of the update to the next handler, you need to set the continue_handling attribute of the update object to True: