PEP 1: Reference to pep2pyramid isn't right #575
Comments
|
That's fine. Just update the README before changing PEP 1 (to make sure it
happens :-).
|
|
@Mariatta summarised the current rendering workflow here: #463 (comment) I'll adapt that into a PR against PEP 1 + the README |
ncoghlan
added a commit
to ncoghlan/peps
that referenced
this issue
Apr 21, 2018
This removes any reference to the technical details of online PEP publication from PEP 1, replacing it with a reference to the README in the PEP repository. It also updates the README with relevant cross-references to the pythondotorg project (based on some process pointers provided by Mariatta Wijaya). Resolves pythonGH-575.
ncoghlan
added a commit
that referenced
this issue
Apr 27, 2018
This removes any reference to the technical details of online PEP publication from PEP 1, replacing it with a reference to the README in the PEP repository. It also updates the README with relevant cross-references to the pythondotorg project (based on some process pointers provided by Mariatta Wijaya). Resolves GH-575.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
PEP 1 references pep2pyramid.py in a footnote in https://www.python.org/dev/peps/pep-0001/#pep-formats-and-templates, which describes how PEPs are generated for http://legacy.python.org/dev/peps/
The relevant code for https://www.python.org/dev/peps/ is in the pythondotorg repo.
That section and the linked footnote should be adjusted to either be independent of how the website works, or else to be accurate for the current site.
@warsaw @gvanrossum Any preference on how we fix that?
I'm personally inclined towards:
The text was updated successfully, but these errors were encountered: