Skip to content

GH-145914: Fill newly created tuple with Py_None instead of NULL - #145913

Closed
sergey-miryanov wants to merge 3 commits into
python:mainfrom
sergey-miryanov:feat/tuple-with-pynone
Closed

sergey-miryanov wants to merge 3 commits into
python:mainfrom
sergey-miryanov:feat/tuple-with-pynone

Conversation

@sergey-miryanov

@sergey-miryanov sergey-miryanov commented Mar 13, 2026 •

Copy link
Copy Markdown
Contributor

Use Py_None instead of NULL in PyTuple_New. This ensures that the tuple is well constructed immediately after calling PyTuple_New.

@sergey-miryanov sergey-miryanov changed the title Fill newly created tuple with Py_None instead of NULL GH-145914: Fill newly created tuple with Py_None instead of NULL Mar 13, 2026
@sergey-miryanov
sergey-miryanov marked this pull request as ready for review March 14, 2026 11:32
@picnixz

picnixz commented Mar 14, 2026

Copy link
Copy Markdown
Member

I'm adding a DO-NOT-MERGE until we address the concern of possibly breaking things downstream on the issue.

@sergey-miryanov

Copy link
Copy Markdown
Contributor Author

Close, see issue.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants