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

FFI definitions for Python3.11 and later frame access #4762

Open
davidhewitt opened this issue Dec 3, 2024 Discussed in #4759 · 0 comments
Open

FFI definitions for Python3.11 and later frame access #4762

davidhewitt opened this issue Dec 3, 2024 Discussed in #4759 · 0 comments

Comments

@davidhewitt
Copy link
Member

davidhewitt commented Dec 3, 2024

Discussed in #4759

Originally posted by dimaqq December 3, 2024
Back in 3.9, I used frame->f_stacktop but that got removed in 3.10 and that's reflected in the rust bindings.

Then (for some other purpose) I used frame->f_valuestack but got got removed in 3.11 together with the frame struct reorganisation (the struct is effectively private), and that too is reflected in the rust bindings.

3.11 did bring in an alternative API: PyFrame_GetLocals, etc. I don't see this in the rust bindings, but maybe I'm not looking in the right place?

What's the PyO3 recommended way to poke into the Python stack?


... looks to me like pyframe.rs bindings are simply out of date, PRs to update the FFI definitions very welcome!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant