Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

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

Provide feedback

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

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[3.14] GH-134774: fix 'Py_DEBUG': macro redefinition warnings for Windows debug builds#134791

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.

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

Already on GitHub?Sign in to your account

Merged
zooba merged 2 commits intopython:3.14fromchris-eibl:fix_Py_DEBUG_warnings_3.14
May 27, 2025

Conversation

chris-eibl
Copy link
Member

@chris-eiblchris-eibl commentedMay 27, 2025
edited by bedevere-appbot
Loading

Since PR#134211 / issue#133779 was packported to 3.14, Windows debug builds show more than thousand such warnings:

pyconfig.h(390,16): warning C4005: 'Py_DEBUG': macro redefinition

This stems from

cpython/PC/pyconfig.h

Lines 97 to 100 inb6e624a

/* _DEBUG implies Py_DEBUG */
#ifdef_DEBUG
# definePy_DEBUG 1
#endif

which got added in the above PR, but rather belong to PR#131944 / issue#131942 and should just be deleted.

@chris-eibl
Copy link
MemberAuthor

Sorry for the other PR: I've messed up and immediately closed again.

So sorry for the churn but I never did a PR against something else than main before.

Had to get 3.14 into my fork since when I've created it some time ago I chose the recommended "only main branch" option.

This seems correct now, but cannot do anything more regarding the other PR than immediately closing :(

Copy link
Member

@serhiy-storchakaserhiy-storchaka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

This code exists in main. Should not we start with main?

@chris-eibl
Copy link
MemberAuthor

The removed lines were just erroneously part of the backport#134211 and belong to a different issue#131942 which is "good" on main. Neither main nor 3.13, etc, are affected. Only 3.14. See also#134774 (comment):

Yeah, probably just a bad backport. Make a PR directly against the 3.14 branch, and include [3.14] at the start of the title to satisfy the backport checker.

Comment on lines -97 to -100
/* _DEBUG implies Py_DEBUG */
#ifdef_DEBUG
# definePy_DEBUG 1
#endif
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Isn't this the one we want to keep? The earlier definition is the new one, to fix an issue with.lib selection.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Oh I see, the rest of that change didn't get backported. This is fine

chris-eibl reacted with thumbs up emoji
@zoobazooba merged commit6c74700 intopython:3.14May 27, 2025
44 checks passed
@chris-eiblchris-eibl deleted the fix_Py_DEBUG_warnings_3.14 branchMay 28, 2025 03:59
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@zoobazoobazooba left review comments

@serhiy-storchakaserhiy-storchakaserhiy-storchaka left review comments

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

3 participants
@chris-eibl@zooba@serhiy-storchaka

[8]ページ先頭

©2009-2025 Movatter.jp