Skip to content

gh-110275: Named tuple's __replace__() now raises TypeError for invalid arguments #110299

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 5 commits into from
Dec 4, 2023
Merged

gh-110275: Named tuple's __replace__() now raises TypeError for invalid arguments #110299

merged 5 commits into from
Dec 4, 2023

Conversation

@serhiy-storchaka
Copy link
Member

@serhiy-storchaka serhiy-storchaka commented Oct 3, 2023 •
edited by bedevere-app bot
Loading

@bedevere-app bedevere-app bot mentioned this pull request Oct 3, 2023
Closed
@serhiy-storchaka serhiy-storchaka changed the title gh-110275: Named tuple's __replace__() now raise TypeError for invalid arguments gh-110275: Named tuple's __replace__() now raises TypeError for invalid arguments Oct 3, 2023
@serhiy-storchaka serhiy-storchaka merged commit c74e9fb into python:main Dec 4, 2023
@serhiy-storchaka serhiy-storchaka deleted the namedtuple-replace-invalid-keyword branch December 4, 2023 11:30
aisk pushed a commit to aisk/cpython that referenced this pull request Feb 11, 2024
@serhiy-storchaka @aisk
pythongh-110275: Named tuple's __replace__() now raises TypeError for…
97767fc 
… invalid arguments (pythonGH-110299)
Glyphack pushed a commit to Glyphack/cpython that referenced this pull request Sep 2, 2024
@serhiy-storchaka @Glyphack
pythongh-110275: Named tuple's __replace__() now raises TypeError for…
78a88b7 
… invalid arguments (pythonGH-110299)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@rhettinger rhettinger Awaiting requested review from rhettinger rhettinger is a code owner

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

@serhiy-storchaka