-
Notifications
You must be signed in to change notification settings - Fork 5.6k
Full Support for Bot API 8.3 #4676
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
❌ 1 Tests Failed:
View the top 1 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
Co-authored-by: Bibo-Joshi <22366557+Bibo-Joshi@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thank you for the PR Pool! I went through the changes a first time and left some comments, nothing mejor though.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot reviewed 16 out of 16 changed files in this pull request and generated no comments.
Comments suppressed due to low confidence (2)
tests/_payment/stars/test_transactionpartner.py:498
- The equality test creates a TransactionPartnerChat without explicitly passing the 'gift' parameter, while the fixture instance includes it. This may lead to unexpected behavior if 'gift' does not have a consistent default; consider passing 'gift' explicitly or documenting the default behavior.
b = TransactionPartnerChat(
chat=self.chat,
tests/_payment/stars/test_transactionpartner.py:475
- [nitpick] Using the literal 'err' as the default value in getattr for verifying slots might mask cases where an attribute's value is legitimately 'err'. Consider using a unique sentinel value to reliably detect missing attributes.
for attr in inst.__slots__:
Co-authored-by: Bibo-Joshi <22366557+Bibo-Joshi@users.noreply.github.com>
Co-authored-by: Bibo-Joshi <22366557+Bibo-Joshi@users.noreply.github.com>
First take, needs to be extended
when ready closes #4677
.. 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 the Stability 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:
Added new constants at
telegram.constants
and shortcuts to them as class variablesLink new and existing constants in docstrings instead of hard-coded numbers and strings
Add new message types to
telegram.Message.effective_attachment
Added new handlers for new update types
telegram.ext.ConversationHandler
Added new filters for new message (sub)types
Added or updated documentation for the changed class(es) and/or method(s)
Added the new method(s) to
_extbot.py
Added or updated
bot_methods.rst
Updated the Bot API version number in all places:
README.rst
(including the badge) andtelegram.constants.BOT_API_VERSION_INFO
Added logic for arbitrary callback data in
telegram.ext.ExtBot
for new methods that either accept areply_markup
in some form or have a return type that is/containstelegram.Message