Skip to content
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

fix(api): configure_scope deprecation warning #3351

Merged

Conversation

szokeasaurusrex
Copy link
Member

Although configure_scope was meant to be deprecated since Sentry
SDK 2.0.0, calling configure_scope did not raise a deprecation
warning. Now, it does.

Fixes #3346

Copy link

codecov bot commented Jul 25, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 79.78%. Comparing base (4aa4c01) to head (6ad6b96).

✅ All tests successful. No failed tests found.

Additional details and impacted files
@@                          Coverage Diff                          @@
##           szokeasaurusrex/configure-scope-2    #3351      +/-   ##
=====================================================================
- Coverage                              79.79%   79.78%   -0.02%     
=====================================================================
  Files                                    133      133              
  Lines                                  14319    14321       +2     
  Branches                                3009     3009              
=====================================================================
  Hits                                   11426    11426              
  Misses                                  2071     2071              
- Partials                                 822      824       +2     
Files Coverage Δ
sentry_sdk/api.py 79.20% <100.00%> (+0.33%) ⬆️

... and 2 files with indirect coverage changes

@szokeasaurusrex szokeasaurusrex linked an issue Jul 26, 2024 that may be closed by this pull request
Although `configure_scope` was meant to be deprecated since Sentry
SDK 2.0.0, calling `configure_scope` did not raise a deprecation
warning. Now, it does.

Fixes #3346
@szokeasaurusrex szokeasaurusrex force-pushed the szokeasaurusrex/configure-scope-2 branch from 4aa4c01 to 1d17d57 Compare July 26, 2024 11:57
@szokeasaurusrex szokeasaurusrex force-pushed the szokeasaurusrex/configure-scope-3-deprecation branch from 6ad6b96 to 6f11f50 Compare July 26, 2024 11:57
Base automatically changed from szokeasaurusrex/configure-scope-2 to master July 26, 2024 13:27
@szokeasaurusrex szokeasaurusrex merged commit 6f11f50 into master Jul 26, 2024
120 checks passed
@szokeasaurusrex szokeasaurusrex deleted the szokeasaurusrex/configure-scope-3-deprecation branch July 26, 2024 13:27
arjennienhuis pushed a commit to arjennienhuis/sentry-python that referenced this pull request Sep 30, 2024
Although `configure_scope` was meant to be deprecated since Sentry
SDK 2.0.0, calling `configure_scope` did not raise a deprecation
warning. Now, it does.

Fixes getsentry#3346
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.

Deprecate sentry_sdk.configure_scope
2 participants