-
Notifications
You must be signed in to change notification settings - Fork 527
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
Small APIdocs improvement #2828
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.
Looks good, see comment
|
||
:param value: The level to set. | ||
""" | ||
logger.warning( |
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.
@antonpirker Why are you emitting the warning with logger
? When I have had to emit deprecation warnings, I usually do so as follows:
warnings.warn("blah blah blah", DeprecationWarning, stacklevel=2)
Is there any significant difference with using logger.warning
vs warnings.warn
? Do we have a preference in the SDKs?
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.
Just used it because all the other deprecation warnings in that file do it the same way.
This PR makes sure all apidocs are recreated always (by deleting an eventually existing
docs/_build
folder) and also adds some minor changes toset_level
andset_tag
to make the types of parameters clear.This is related to this Docs PR: getsentry/sentry-docs#5432