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

PEP 1 and 12: Remove optional Content-Type from templates #3454

Merged
merged 1 commit into from
Sep 28, 2023

Conversation

hugovk
Copy link
Member

@hugovk hugovk commented Sep 27, 2023

Fixes #2500.

But following issue #10 / PR #3418, all PEPs now have an .rst extension, so we no longer need the optional header for new PEPs.


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

Copy link
Member

@AA-Turner AA-Turner left a comment

Choose a reason for hiding this comment

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

As it happens I have a draft branch that removes Content-Type from all PEPs. But I thought likely too disruptive given the spate of recent changes; this is a nice compromise. Thanks!

A

@AA-Turner AA-Turner merged commit 3b5f6f4 into python:main Sep 28, 2023
@hugovk hugovk deleted the rm-optional-content-type branch September 28, 2023 04:31
@hugovk hugovk mentioned this pull request Sep 28, 2023
13 tasks
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.

Is Content-Type optional?
5 participants