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

gh-134632: Fixbuild-details.json to useINCLUDEPY path#134633

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

Open
mgorny wants to merge3 commits intopython:main
base:main
Choose a base branch
Loading
frommgorny:pep739-includepy-134632

Conversation

mgorny
Copy link
Contributor

@mgornymgorny commentedMay 24, 2025
edited by AA-Turner
Loading

Fixbuild-details.json generation to useINCLUDEPY, in order to reference thepythonX.Y subdirectory of the include directory, as required inPEP-0739, instead of the top-level include directory.

Fix ``build-details.json`` generation to use ``INCLUDEPY``, in order toreference the ``pythonX.Y`` subdirectory of the include directory, asrequired in :pep:`739`, instead of the top-level include directory.
@mgorny
Copy link
ContributorAuthor

CC@FFY00

Copy link
Contributor

@sharktidesharktide left a comment

Choose a reason for hiding this comment

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

LGTM!

@ZeroIntensityZeroIntensity added buildThe build process and cross-build needs backport to 3.14bugs and security fixes labelsMay 25, 2025
Comment on lines +2 to +3
reference the ``pythonX.Y`` subdirectory of the include directory, as
required in :pep:`739`, instead of the top-level include directory.
Copy link
Member

Choose a reason for hiding this comment

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

If required by the PEP, we should have a test enforcing this contract?

Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

Do you have anything specific in mind? Checking that the value in the generatedbuild-details.json ends withpythonX.Y specifically, or something deeper?

Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

I've added a test that checks that the values ofc_api.include andc_api.pkgconfig_path (if present) point to valid directories with necessary files.

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

@AA-TurnerAA-TurnerAA-Turner left review comments

@emmatypingemmatypingemmatyping approved these changes

@sharktidesharktidesharktide approved these changes

Assignees
No one assigned
Labels
awaiting core reviewbuildThe build process and cross-buildneeds backport to 3.14bugs and security fixes
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

5 participants
@mgorny@AA-Turner@emmatyping@sharktide@ZeroIntensity

[8]ページ先頭

©2009-2025 Movatter.jp