Skip to content

Conversation

@ericsnowcurrently
Copy link
Member

@ericsnowcurrentlyericsnowcurrently commented Oct 31, 2023

@ericsnowcurrentlyericsnowcurrently changed the title gh-76785: Return an ExceptionSnapshot from Interpreter.run().gh-76785: Return an ExceptionSnapshot From Interpreter.run()Oct 31, 2023
@ericsnowcurrentlyericsnowcurrentlyforce-pushed the interp-run-return-exc-info branch 4 times, most recently from 5443e2c to 3f56dbfCompareNovember 2, 2023 16:18
@ericsnowcurrentlyericsnowcurrentlyforce-pushed the interp-run-return-exc-info branch from 3f56dbf to f25d3f9CompareNovember 3, 2023 22:36
ericsnowcurrently added a commit that referenced this pull request Nov 6, 2023
…1715) I added _Py_excinfo to the internal API (and added its functions in Python/errors.c) in gh-111530 (9322ce9). Since then I've had a nagging sense that I should have added the type and functions in its own PR. While I do plan on using _Py_excinfo outside crossinterp.c very soon (see gh-111572/gh-111573), I'd still feel more comfortable if the _Py_excinfo stuff went in as its own PR. Hence, here we are. (FWIW, I may combine that with gh-111572, which I may, in turn, combine with gh-111573. We'll see.)
@ericsnowcurrentlyericsnowcurrentlyforce-pushed the interp-run-return-exc-info branch from f25d3f9 to 9f83af7CompareNovember 6, 2023 19:14
hugovk pushed a commit to hugovk/cpython that referenced this pull request Nov 8, 2023
…ythongh-111715) I added _Py_excinfo to the internal API (and added its functions in Python/errors.c) in pythongh-111530 (9322ce9). Since then I've had a nagging sense that I should have added the type and functions in its own PR. While I do plan on using _Py_excinfo outside crossinterp.c very soon (see pythongh-111572/pythongh-111573), I'd still feel more comfortable if the _Py_excinfo stuff went in as its own PR. Hence, here we are. (FWIW, I may combine that with pythongh-111572, which I may, in turn, combine with pythongh-111573. We'll see.)
@ericsnowcurrentlyericsnowcurrently changed the title gh-76785: Return an ExceptionSnapshot From Interpreter.run()gh-76785: Return an "excinfo" Object From Interpreter.run()Nov 23, 2023
@ericsnowcurrentlyericsnowcurrently marked this pull request as ready for review November 23, 2023 00:48
@ericsnowcurrentlyericsnowcurrently enabled auto-merge (squash) November 23, 2023 00:48
@ericsnowcurrentlyericsnowcurrently merged commit 9e56eed into python:mainNov 23, 2023
@ericsnowcurrentlyericsnowcurrently deleted the interp-run-return-exc-info branch November 23, 2023 00:55
aisk pushed a commit to aisk/cpython that referenced this pull request Feb 11, 2024
…ythongh-111715) I added _Py_excinfo to the internal API (and added its functions in Python/errors.c) in pythongh-111530 (9322ce9). Since then I've had a nagging sense that I should have added the type and functions in its own PR. While I do plan on using _Py_excinfo outside crossinterp.c very soon (see pythongh-111572/pythongh-111573), I'd still feel more comfortable if the _Py_excinfo stuff went in as its own PR. Hence, here we are. (FWIW, I may combine that with pythongh-111572, which I may, in turn, combine with pythongh-111573. We'll see.)
Glyphack pushed a commit to Glyphack/cpython that referenced this pull request Sep 2, 2024
…ythongh-111715) I added _Py_excinfo to the internal API (and added its functions in Python/errors.c) in pythongh-111530 (9322ce9). Since then I've had a nagging sense that I should have added the type and functions in its own PR. While I do plan on using _Py_excinfo outside crossinterp.c very soon (see pythongh-111572/pythongh-111573), I'd still feel more comfortable if the _Py_excinfo stuff went in as its own PR. Hence, here we are. (FWIW, I may combine that with pythongh-111572, which I may, in turn, combine with pythongh-111573. We'll see.)
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@ericsnowcurrently