← 返回首页
gh-76785: Return an "excinfo" Object From Interpreter.run() by ericsnowcurrently · Pull Request #111573 · python/cpython · GitHub
Skip to content

Navigation Menu

Toggle navigation
Sign in
Appearance settings
Search or jump to...

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted
Cancel Submit feedback

Saved searches

Use saved searches to filter your results more quickly

Cancel Create saved search
Appearance settings
Resetting focus

gh-76785: Return an "excinfo" Object From Interpreter.run()#111573

Merged
ericsnowcurrently merged 4 commits into
python:mainfrom
ericsnowcurrently:interp-run-return-exc-info
Nov 23, 2023
Merged

gh-76785: Return an "excinfo" Object From Interpreter.run()#111573
ericsnowcurrently merged 4 commits into
python:mainfrom
ericsnowcurrently:interp-run-return-exc-info

Conversation

ericsnowcurrently commented Oct 31, 2023 •
edited by bedevere-app Bot
Loading

Copy link
Copy Markdown
Member

bedevere-app Bot mentioned this pull request Oct 31, 2023
Closed
ericsnowcurrently changed the title gh-76785: Return an ExceptionSnapshot from Interpreter.run(). gh-76785: Return an ExceptionSnapshot From Interpreter.run() Oct 31, 2023
ericsnowcurrently force-pushed the interp-run-return-exc-info branch 4 times, most recently from 5443e2c to 3f56dbf Compare November 2, 2023 16:18
ericsnowcurrently mentioned this pull request Nov 3, 2023
Merged
ericsnowcurrently force-pushed the interp-run-return-exc-info branch from 3f56dbf to f25d3f9 Compare November 3, 2023 22:36
ericsnowcurrently added a commit that referenced this pull request Nov 6, 2023
gh-76785: Move _Py_excinfo Functions Out of the Internal C-API (gh-11… …
d4426e8
…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.)
ericsnowcurrently force-pushed the interp-run-return-exc-info branch from f25d3f9 to 9f83af7 Compare November 6, 2023 19:14
hugovk pushed a commit to hugovk/cpython that referenced this pull request Nov 8, 2023
pythongh-76785: Move _Py_excinfo Functions Out of the Internal C-API (p… …
8ac1b5b
…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.)
ericsnowcurrently force-pushed the interp-run-return-exc-info branch from 9f83af7 to dfff3e3 Compare November 23, 2023 00:33
ericsnowcurrently changed the title gh-76785: Return an ExceptionSnapshot From Interpreter.run() gh-76785: Return an "excinfo" Object From Interpreter.run() Nov 23, 2023
ericsnowcurrently marked this pull request as ready for review November 23, 2023 00:48
ericsnowcurrently enabled auto-merge (squash) November 23, 2023 00:48
ericsnowcurrently merged commit 9e56eed into python:main Nov 23, 2023
ericsnowcurrently 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
pythongh-76785: Move _Py_excinfo Functions Out of the Internal C-API (p… …
34fab73
…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.)
aisk pushed a commit to aisk/cpython that referenced this pull request Feb 11, 2024
pythongh-76785: Return an "excinfo" Object From Interpreter.run() (py… …
3a10f50
…thongh-111573)
Glyphack pushed a commit to Glyphack/cpython that referenced this pull request Sep 2, 2024
pythongh-76785: Move _Py_excinfo Functions Out of the Internal C-API (p… …
049be32
…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
pythongh-76785: Return an "excinfo" Object From Interpreter.run() (py… …
85f99b2
…thongh-111573)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Show hidden characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

skip news

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

Footer

© 2026 GitHub, Inc.