Skip to content

bpo-46038: Mark /configure file as generated in .gitattributes #30031

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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from

Conversation

arhadthedev
Copy link
Member

@arhadthedev arhadthedev commented Dec 10, 2021

configure is regenerated from configure.ac using a custom container with appropriate version of tools (quay.io/tiran/cpython_autoconf by Christian Heimes). As a result, configure falls into the same category as files generated by Argument Clinic, Freeze and Parser/asdl_c.py. Due to size and churn of these artifacts, they are marked in .gitattributes as generated so GitHub Pull Request Diff Viewer collapses them into a short notification. This pull request does the same for configure.

Actually, configure diff is so large that sometimes it crosses a threshold and GitHub collapses it by force with "Large diffs are not rendered by default" or even "xxx additions, yyy deletions not shown because the diff is too large. Please use a local Git client to view these changes". See GH-29756 as an extreme example and https://github.com/python/cpython/commits/main/configure for an average.

I believe this PR does not need a NEWS entry because the change is relevant only for a GitHub-hosted copy.

https://bugs.python.org/issue46038

configure is regenerated from configure.ac using a custom container
with appropriate version of tools (quay.io/tiran/cpython_autoconf
by Christian Heimes).

As a result, configure falls into the same category as files generated
by Argument Clinic, Freeze and Parser/asdl_c.py. Due to size and churn
of these artifacts, they are marked in .gitattributes as generated so
GitHub Pull Request Diff Viewer collapses them into a short
notification. This commit does the same for configure.

Actually, configure diff is so large that sometimes it crosses
a threshold and GitHub collapses it by force with "Large diffs are not
rendered by default" or even "xxx additions, yyy deletions not shown
because the diff is too large. Please use a local Git client to view
these changes". See pythonGH-29756 as an extreme example and
<https://github.com/python/cpython/commits/main/configure> for
an average.
@erlend-aasland
Copy link
Contributor

I'd say we backport this to 3.10 and 3.9, @tiran.

@github-actions
Copy link

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 Jan 10, 2022
Copy link
Contributor

@taleinat taleinat left a comment

Choose a reason for hiding this comment

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

LGTM but I know very little about autoconf.

@tiran, should this be merged? And should it be backported?

@arhadthedev
Copy link
Member Author

Closing in favor of #30745.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting merge skip news stale Stale PR or inactive for long period of time.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants