-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
List BDFL Delegates and target Python version in the PEP Index #1012
Comments
Reading through https://github.com/python/pythondotorg/blob/master/peps/converters.py indicates that there shouldn't be any compatibility issues that would break rendering outright, which means the key item to check for will be how a table with more columns displays at the default python.org viewport width. |
Sounds like a good idea. |
A column for the Python target version has been added via PR #3434. For example: https://peps.python.org/#open-peps-under-consideration |
I don't think this has turned out to be the case in practice: most PEPs are decided by the SC as a whole and without a delegate. And I think trying a add another column might be squeezing too much onto the screen. (Mitigations could include removing the menu from the left on desktop, or not displaying this column for narrower mobile.) For these two reasons, I suggest we don't add the delegate to the tables, and close this issue. |
Agreed. No need for the extra column. |
Fourth-ed. A |
The changes to PEP 1 following the appointment of the first Steering Council have made the BDFL-Delegate role more significant, since every PEP is now expected to have a delegate appointed (even in cases where the delegate is an SC member speaking on behalf of the SC).
However, this information isn't presented in the PEP Index overview - it's only visible on the individual project pages.
Similarly, which version a PEP is targeting is very useful overview information, as a draft PEP targeting the next release (currently 3.8) needs different handling from one targeting a subsequent release.
Updating the PEP 0 generator to include that additional information would be reasonably straightforward (as it already reads in all the headers for all the PEPs), so the main complication would be to ensure that the python.org PEP index rendering doesn't break (as discussed in https://github.com/python/peps/blob/master/README.rst#generating-html-for-pythonorg )
The text was updated successfully, but these errors were encountered: