-
Notifications
You must be signed in to change notification settings - Fork 5.7k
API 7.5 new classes #4311
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
API 7.5 new classes #4311
Conversation
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.
Hey : ) I noticed the "WIP" label too late, so here you already have somen comment 😅
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.
Hey, thanks for the updates! I went throug the new changes and admittedly only skimmed the tests 😅
I left a few more comments
@@ -133,15 +263,16 @@ def test_de_json_star_transaction_localization(self, star_transaction, tz_bot, b | |||
assert st_bot.date.tzinfo == UTC | |||
assert st_offset == tz_bot_offset | |||
|
|||
def test_to_dict(self, star_transaction): | |||
def test_to_dict(self): | |||
st = star_transaction() |
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.
did you mean to use this as fixuter instead, i.e. pass it as argument? same in the other tests
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.
I had done that before but I actually wanted to use the return value in TestStarTransactionsBase
, so I kept it as a function
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.
Mh, I see. Might something like this be of use? https://stackoverflow.com/a/63047695/10606962
I'm okay with keeping as is, but it's at least something that future-us will likely stumble over if we have re-touch tests.
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.
LGTM just left me know if you want to change something about the tests or keep it as is :)
I'll keep the tests as is for now. |
Checklist
.. versionadded:: NEXT.VERSION
,.. versionchanged:: NEXT.VERSION
or.. deprecated:: NEXT.VERSION
to the docstrings for user facing changes (for methods/class descriptions, arguments and attributes)CSI standard <https://standards.mousepawmedia.com/en/stable/csi.html>
__AUTHORS.rst
(optional)__all__
sStability Policy <https://docs.python-telegram-bot.org/stability_policy.html>
_ in case of deprecations or changes to documented behaviorIf the PR contains API changes (otherwise, you can ignore this passage)
Checked the Bot API specific sections of the Stability Policy
New classes:
self._id_attrs
and corresponding documentation__init__
acceptsapi_kwargs
as kw-onlyAdded new shortcuts:
~telegram.Chat
& :class:~telegram.User
for all methods that acceptchat/user_id
~telegram.Message
for all methods that acceptchat_id
andmessage_id
~telegram.Message
shortcuts: Addeddo_quote
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
andREADME_RAW.rst
(including the badge), as well astelegram.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/contains :class:~telegram.Message