• BotCommandScope* is just for input, never output (at least for now), so we don't really need a proper de_json. But I realized that only after I had implemented it … If you think it's superfluous, we can remove
• Leaving the checklists empty for now so we can go over them once in the end.

Checklist for PRs

• Added .. versionadded:: version, .. versionchanged:: version or .. deprecated:: version to the docstrings for user facing changes (for methods/class descriptions, arguments and attributes)
• Created new or adapted existing unit tests
• Added myself alphabetically to AUTHORS.rst (optional)

If the PR contains API changes (otherwise, you can delete this passage)

• New classes:

  • Added self._id_attrs and corresponding documentation
  • __init__ accepts **_kwargs

• Added new shortcuts:

  • In Chat & User for all methods that accept chat/user_id -> We need to deprecate Chat.get_members_count in favor of a new Chat.get_member_count and the same for kick_chat_member -> ban_chat_member
  • [ ] In Message for all methods that accept chat_id and message_id
  • [ ] For new Message shortcuts: Added quote argument if methods accepts reply_to_message_id
  • [ ] In CallbackQuery for all methods that accept either chat_id and message_id or inline_message_id

• If relevant:

  • Added new constants at telegram.constants and shortcuts to them as class variables
  • [ ] Added new handlers for new update types
  • [ ] Added new filters for new message (sub)types
  • Added or updated documentation for the changed class(es) and/or method(s)
  • Updated the Bot API version number in all places: README.rst and README_RAW.rst (including the badge), as well as telegram.constants.BOT_API_VERSION
  • [ ] Added logic for arbitrary callback data in tg.ext.Bot for new methods that either accept a reply_markup in some form or have a return type that is/contains telegram.Message