Skip to content

gh-153374: Better way to clear name error suggestion#141389

Open
Locked-chess-official wants to merge 7 commits into
python:mainfrom
Locked-chess-official:clear_NameError_suggestion
Open

gh-153374: Better way to clear name error suggestion#141389
Locked-chess-official wants to merge 7 commits into
python:mainfrom
Locked-chess-official:clear_NameError_suggestion

Conversation

@Locked-chess-official

@Locked-chess-official Locked-chess-official commented Nov 11, 2025

Copy link
Copy Markdown
Contributor

Thanks blhsing. This way don't need to change the C code.

@github-actions

github-actions Bot commented May 2, 2026

Copy link
Copy Markdown

This PR is stale because it has been open for 30 days with no activity.

@github-actions github-actions Bot added the stale Stale PR or inactive for long period of time. label May 2, 2026
@sergey-miryanov

Copy link
Copy Markdown
Contributor

I propose you to open a new issue if you want to continue work on this.

@StanFromIreland

Copy link
Copy Markdown
Member

Yes this needs a new issue, closing for now.

@Locked-chess-official Locked-chess-official changed the title gh-138890: Better way to clear name error suggestion gh-153374: Better way to clear name error suggestion Jul 9, 2026
@Locked-chess-official

Copy link
Copy Markdown
Contributor Author

@StanFromIreland new issue is ready

Comment thread Lib/traceback.py Outdated
@brijkapadia

Copy link
Copy Markdown
Contributor

You should also probably add a regression test in case the bytecode changes again or something similar happens

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

Labels

awaiting review stale Stale PR or inactive for long period of time.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants