FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

Fix docstring Args entries that name a parameter the class does not take by darkdi · Pull Request #5326 · python-telegram-bot/python-telegram-bot · GitHub

Fix docstring Args entries that name a parameter the class does not take - #5326

Open
darkdi wants to merge 3 commits into
python-telegram-bot:masterfrom
darkdi:fix/docstring-arg-names
Open

Fix docstring Args entries that name a parameter the class does not take#5326
darkdi wants to merge 3 commits into
python-telegram-bot:masterfrom
darkdi:fix/docstring-arg-names

Conversation

darkdi commented Aug 7, 2026

Copy link
Copy Markdown

Six Args: entries name something the callable does not take.

Four are the PaidMedia subclasses. Each documents type under Args:, but none of their __init__ takes it: super().__init__(type=PaidMedia.PREVIEW) and so on. MessageOrigin* is built exactly the same way and documents type only under Attributes:, which is what made me read these as a slip rather than a house style. The Attributes: entry stays in all four.

decrypt documents a file argument it does not have, and ApplicationBuilder.get_updates_proxy documents proxy, copied from the proxy method above it. That one had to be rewrapped to stay under 99 characters.

ruff check and ruff format --check are clean on the three files with the pinned ruff==0.16.0. If the type entries are deliberate I will drop that part of the change.

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant


Back | FazBrowse Home | New Git URL