Drop explicit type conversions in __init__
s
#3056
Merged
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.
Addresses the second part of and closes #2901.
I double checked: numbers and strings are indeed different things in json, so this won't be a problem. My concerns in #2901 (comment) probably came from my subconscious recalling that keys can only be strings in json, which is why
json.dumps({1: '1'}) == '{"1": 1}'
andjson.loads('{"1": 1}') == {"1": 1}
.This also makes
RetryAfter.retry_after
an integer b/c that's what TG documents (this is a tiny breaking change) and adds some missing docs to the error module.Checklist for PRs
.. versionadded:: version
,.. versionchanged:: version
or.. deprecated:: version
to the docstrings for user facing changes (for methods/class descriptions, arguments and attributes)AUTHORS.rst
(optional)__all__
s