| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
PyInterpreterState.eval_frame (PEP 523) now requires a new mandatory tstate parameter (PyThreadState*).
|
This change is backward incompatible and changes the PEP 523. I would prefer to have it carefully reviewed ;-) |
Sorry, something went wrong.
In order to keep backward compatibility, can we use a new function to do this action? |
Sorry, something went wrong.
PyInterpreterState.eval_frame is a structure field. What do you mean? |
Sorry, something went wrong.
There was a problem hiding this comment.
It can happen from the contributors who are not familiar with the codebase.
@shihai1991 I think that the snippet I attach links below will help your future contribution.
Line 25 in 2bc43cd
cpython/Include/internal/pycore_pystate.h
Line 109 in 9def81a
@vstinner
Looks good to me.
Sorry, something went wrong.
Sorry, i didn't express cleary. I just worried about whether we have external user use _PyEval_EvalFrameDefault(struct _frame *f, int exc)(although it's a inner function). |
Sorry, something went wrong.
|
frame_eval is specified by https://www.python.org/dev/peps/pep-0523/ The question if it should be public or not is discussed at https://bugs.python.org/issue38500 At least, the API (frame_eval) is used by PyCharm to implement their debugger ;-) |
Sorry, something went wrong.
|
I don't think this should go in until bpo-38500 is resolved. |
Sorry, something went wrong.
|
I included this change into PR #17340. I close this PR. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
PyInterpreterState.eval_frame (PEP 523) now requires a new mandatory
tstate parameter (PyThreadState*).
https://bugs.python.org/issue38818