You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am writing in to let you know about a change in our next major release (likely 3.0.0), which will break strawberry.extensions.tracing.sentry by making it impossible to import this module when sentry-sdk>=3.0.0 is installed. Specifically, we will remove sentry_sdk.configure_scope, which you are importing in the strawberry.extensions.tracing.sentry module.
Since the Sentry tracing module built into Strawberry is already deprecated (sentry-sdk natively supports Strawberry now), I would recommend removing the strawberry.extensions.tracing.sentry module completely. Otherwise, it would be a good idea to handle the ImportError or to migrate to the new API replacing configure_scope.
We still have no timeline on when we are releasing Sentry SDK 3.0.0, but it will likely only be released several weeks or months from now – so, you still have time before this breaks. Just wanted to give a heads up.
Upvote & Fund
We're using Polar.sh so you can upvote and help fund this issue.
We receive the funding once the issue is completed & confirmed by you.
Thank you in advance for helping prioritize & fund our backlog.
The text was updated successfully, but these errors were encountered:
Hi, I am one of the maintainers of the Sentry Python SDK.
I am writing in to let you know about a change in our next major release (likely
3.0.0
), which will breakstrawberry.extensions.tracing.sentry
by making it impossible to import this module whensentry-sdk>=3.0.0
is installed. Specifically, we will removesentry_sdk.configure_scope
, which you are importing in thestrawberry.extensions.tracing.sentry
module.Since the Sentry tracing module built into Strawberry is already deprecated (
sentry-sdk
natively supports Strawberry now), I would recommend removing thestrawberry.extensions.tracing.sentry
module completely. Otherwise, it would be a good idea to handle theImportError
or to migrate to the new API replacingconfigure_scope
.We still have no timeline on when we are releasing Sentry SDK
3.0.0
, but it will likely only be released several weeks or months from now – so, you still have time before this breaks. Just wanted to give a heads up.Upvote & Fund
The text was updated successfully, but these errors were encountered: