-
Notifications
You must be signed in to change notification settings - Fork 5.7k
Improve Warning Categories & Stacklevels #3674
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
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.
nice catches
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'm obviously out of my depth here, but one typo I did catch! :)
Just a related note: stackleveling will get way more fun soon :D https://github.com/python-telegram-bot/python-telegram-bot/projects/8#card-88970053 |
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.
much more extensive testing, I like it
While working on #3673 I noticed that the subscription access to attributes of |
I wonder if there is a way to dynamically inspect the stacklevel and pass the correct value for cases like those... |
@harshil21 I guess there is inspect.stack. I'm not so sure if I want to get the inspect module involved for this 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.
lgtm
Bot
andExtBot
, ensuring that the stacklevel is correct for bothTODO: