


change cmds of CommandHandler into *cmds.Have a chance to use yourself route policy on incoming updates. Modify ssage_handler(fields) to ssage_handler(*fields) Update 5.5.4ĭo a update dispatch as the update's coming. more detail is in example.callback_query Update 5.5.5 change bot.get_file_bytes(file_path, chunk_size) into bot.get_file_bytes(file_obj)Īdd remove and where methods for InlineKeyboard.add group method where methods for InlineKeyboard.Using n_in_executor for synchronous functions Update 5.5.11 Update for Telegram Bot API 6.0 Update 5.7.0 Update for Telegram Bot API 6.1 Update 6.0 I reckon it is lightweight, fast, full implement and only urllib3 dependent. The reason for writing this bot utility is that I wish to run multi telegram bots which could have same or different business logic (route policy) in one process. A telegram bot API client is written in python 3.5+ and currently compatible with Telegram Bot API 5.3 and later.
