- Notifications
You must be signed in to change notification settings - Fork5.7k
Full Support for Bot API 9.0#4756
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Merged
Merged
Uh oh!
There was an error while loading.Please reload this page.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
Co-authored-by: Abdelrahman Elkheir <90580077+aelkheir@users.noreply.github.com>
TG's documentation inconsistently refers to the attributes`can_edit_bio`, `can_edit_name`, and `can_edit_username` as`can_change_bio`, `can_change_name`, and `can_change_username` in thedocstrings of respective bot methods, which is causing sphinx :attr:references to break.
Follow up to#4763. sorry forgot to push before merging.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>Co-authored-by: Abdelrahman Elkheir <90580077+aelkheir@users.noreply.github.com>
Co-authored-by: Hinrich Mahler <22366557+Bibo-Joshi@users.noreply.github.com>
7078059
intomaster 6 checks passed
Uh oh!
There was an error while loading.Please reload this page.
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.
Labels
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Master PR for Bot API 9.0.
When ready,closes#4754 .
Checklist
.. versionadded:: NEXT.VERSION
,.. versionchanged:: NEXT.VERSION
,.. deprecated:: NEXT.VERSION
or.. versionremoved:: NEXT.VERSION
to the docstrings for user facing changes (for methods/class descriptions, arguments and attributes)AUTHORS.rst
(optional)__all__
sIf the PR contains API changes (otherwise, you can ignore this passage)
Checked the Bot API specific sections of theStability Policy
Created a PR to remove functionality deprecated in the previous Bot API release (see here)
New classes:
self._id_attrs
and corresponding documentation__init__
acceptsapi_kwargs
as kw-onlyAdded new shortcuts:
telegram.Chat
&telegram.User
for all methods that acceptchat/user_id
telegram.Message
for all methods that acceptchat_id
andmessage_id
telegram.Message
shortcuts: Addedquote
argument if methods acceptsreply_to_message_id
telegram.CallbackQuery
for all methods that accept eitherchat_id
andmessage_id
orinline_message_id
If relevant:
telegram.constants
and shortcuts to them as class variablestelegram.Message.effective_attachment
telegram.ext.ConversationHandler
_extbot.py
bot_methods.rst
README.rst
(including the badge) andtelegram.constants.BOT_API_VERSION_INFO
telegram.ext.ExtBot
for new methods that either accept areply_markup
in some form or have a return type that is/containstelegram.Message