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

bug-1811299: update eliot to python 3.10 #106

Merged
merged 1 commit into from
Dec 5, 2023
Merged

bug-1811299: update eliot to python 3.10 #106

merged 1 commit into from
Dec 5, 2023

Conversation

willkg
Copy link
Contributor

@willkg willkg commented Dec 4, 2023

This updates Eliot to Python 3.10.13-slim-bullseye. I wanted to update to Python 3.11, but Falcon doesn't support Python 3.11, yet. They will with Falcon 4.0.

We're using bullseye (Debian 11) because we're using that across all our services for now. At some point, we'll switch all our services to bookworm (Debian 12).

"iscoroutinefunction": ANY,
"re": "<module 're' from '/usr/local/lib/python3.9/re.py'>",
"wraps": ANY,
},
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure why updating Python caused this change and didn't look into it.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know how the sentry package extracts the local variables, but my guess is they copy f_locals from the frame object. That has always been one of the weirder corners of Python, or at least since local variables aren't dictionaries anymore, so since the 2.0 release? Updates to f_locals are not reflected in local variables, and updates to local variables are not always reflected in f_locals as well.

I'm not surprised that this kind of change can happen when upgrading Python, and I don't think we care.

@willkg willkg merged commit 52a4001 into main Dec 5, 2023
@willkg
Copy link
Contributor Author

willkg commented Dec 5, 2023

Thank you!

@willkg willkg deleted the bug-1811299-py310 branch January 11, 2024 15:03
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.

2 participants