-
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
[2.0] Small (compatibility) fixes #2663
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, except for one small thing
sentry_sdk/hub.py
Outdated
def _check_python_deprecations(): | ||
# type: () -> None | ||
version = sys.version_info[:2] | ||
|
||
if version == (3, 4) or version == (3, 5): | ||
logger.warning( | ||
"sentry-sdk 2.0.0 will drop support for Python %s.", | ||
"{}.{}".format(*version), | ||
) | ||
logger.warning( | ||
"Please upgrade to the latest version to continue receiving upgrades and bugfixes." | ||
) | ||
# Use this to output logger.warnings for deprecated Python versions | ||
pass |
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 am assuming that we are keeping this method here in case we deprecate any other Python versions in the future?
If so, please update the comment to clarify that we are keeping the method around for future use. With the current comment, the reason why this function still exists is somewhat unclear.
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.
Updated, please check.
An assortment of small fixes that don't really belong in any of the bigger PRs.
General Notes
Thank you for contributing to
sentry-python
!Please add tests to validate your changes, and lint your code using
tox -e linters
.Running the test suite on your PR might require maintainer approval. Some tests (AWS Lambda) additionally require a maintainer to add a special label to run and will fail if the label is not present.
For maintainers
Sensitive test suites require maintainer review to ensure that tests do not compromise our secrets. This review must be repeated after any code revisions.
Before running sensitive test suites, please carefully check the PR. Then, apply the
Trigger: tests using secrets
label. The label will be removed after any code changes to enforce our policy requiring maintainers to review all code revisions before running sensitive tests.