-
Notifications
You must be signed in to change notification settings - Fork 543
Python 3.12 support - RuntimeError #2299
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
Comments
We got to work around this by closing sentry manually at the end of our programs 🤷 |
Thanks for the heads up @Toaster192! |
Would be great to have this fixed now that Python 3.12 is officially released. |
Agreed @jnoordsij. We're currently figuring out what we need to fix for 3.12, this is definitely on the list. |
Looking at #1950, is there some hope hat it will not take month(s) for 3.12 support? Even more so considering that 3.11 was just about (non-technical) metadata, while there's an actual issue with 3.12 right now which is not necessarily a blocker but at least a bit annoying when an application has CLI tools for example where this exception gets raised. |
We have a PR open for supporting 3.12, but we can not give you an estimate on when it will be merged/released: |
I'm also seeing this issue when terminating a Sanic server
|
This also occurs when running migrations in Django.
|
Yes, I think it always happens when the Python interpreter exits while the sentry SDK is 'active'... |
Thanks for all the input! We will try to tackle this soon! |
Hey everybody, Could you give it a try @Toaster192 @robd003 and @ethrgeist ? |
Looks good, CLI and reload spam is gone, thank you very much! 8000 |
Hi team, I am getting this error everytime a program has to exit: I am using python 3.12 and sentry-sdk==1.14.0
|
the fix was released in 1.33.0 |
Problem Statement
Tried using sentry with python 3.12. Ran into newly implemented RuntimeError tests. Want to give a heads up for once there is 3.12 (hopefuly after 3.11 #1950 🤞 ) support that this is something that will probably need fixing(?)
Example traceback (source):
cpython commit adding this "detection": python/cpython@ce558e6
Solution Brainstorm
Some sort of "graceful shutdown" on exit perhaps?
The text was updated successfully, but these errors were encountered: