Skip to content
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

All PEPs: Move to peps/ folder #3418

Merged
merged 22 commits into from
Sep 9, 2023
Merged

Conversation

AA-Turner
Copy link
Member

@AA-Turner AA-Turner commented Sep 3, 2023

Would resolve #10.

cc: @python/pep-editors for views.

I've structured as distinct commits -- the first does the actual move, the following thirteen tackle follow-ups and previous assumptions over file locations.

A


📚 Documentation preview 📚: https://pep-previews--3418.org.readthedocs.build/

Copy link
Member

@hugovk hugovk left a comment

Choose a reason for hiding this comment

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

First up, some extra pre-commit cleanup.

.pre-commit-config.yaml Outdated Show resolved Hide resolved
.pre-commit-config.yaml Outdated Show resolved Hide resolved
.pre-commit-config.yaml Outdated Show resolved Hide resolved
.pre-commit-config.yaml Outdated Show resolved Hide resolved
.pre-commit-config.yaml Outdated Show resolved Hide resolved
.pre-commit-config.yaml Outdated Show resolved Hide resolved
.pre-commit-config.yaml Outdated Show resolved Hide resolved
.pre-commit-config.yaml Outdated Show resolved Hide resolved
.pre-commit-config.yaml Outdated Show resolved Hide resolved
.gitignore Outdated Show resolved Hide resolved
@AA-Turner
Copy link
Member Author

I reviewed the pre-commit guidance---it seems that our usages of types: were mostly redundant due to filtering files to match PEPs, so I've just removed them.

A

- Group ignores by purpose
- Remove 'package'
- Remove 'pep-????.html'
- Allow topic to cover top level or in peps/
.pre-commit-config.yaml Outdated Show resolved Hide resolved
.pre-commit-config.yaml Outdated Show resolved Hide resolved
@AA-Turner
Copy link
Member Author

Out of a slight fear of this going the same way as #2672, please may I ask if anyone has any burning passions against the general proposal to move the PEPs into a sub-folder? (We can tweak implementation details later, of course.)

If all is well, I'd like to set a timeline for merging this -- perhaps Tuesday or Wednesday, if that's not too early?

A

@Rosuav
Copy link
Contributor

Rosuav commented Sep 4, 2023

No burning passions, no. Just a broad "is this worth the effort", but I'm not going to stand in anyone's way.

@AA-Turner
Copy link
Member Author

I'll merge this today, sorry in advance for the review-request spam.

A

@AA-Turner
Copy link
Member Author

I'll keep an eye on https://peps.python.org just in case.

@AA-Turner
Copy link
Member Author

All seems well!

A

@AA-Turner AA-Turner deleted the peps-in-peps branch September 9, 2023 17:53
joshuabambrick added a commit to joshuabambrick/steering-council that referenced this pull request Dec 2, 2023
Current PEPs links are dead since python/peps#3418
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Move peps into subdirectory
5 participants