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
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!
The text was updated successfully, but these errors were encountered:
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!The text was updated successfully, but these errors were encountered: