You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When looking at a PEP page on python.org, it isn't obvious when the PEP was last modified, or how to see recent revisions.
In addition, search engines often aren't displaying useful information. E.g. the Google result for a search of PEPs seems to show the Created: date, which may confuse searchers. E.g. the date listed for PEP 518 in a Google search is May 10, 2016, though this Provisional PEP was most recently updated on Dec 13, 2019.
Describe the solution you'd like
It would be great if the footer of the HTML rendering of each PEP, when served by python.org, included a Last-Modified: date, with a link to the GitHub history for more information. It could go after the Source link at the bottom of the page. E.g.
Given the peps git repo obtained via that process, it seems to take less than 20 seconds to get the latest modification date of all the PEPs via e.g. even using the shell pipeline listed at How to retrieve the last modification date of all files in a git repository - Server Fault, so I don't think there would be much overhead to maintaining this information.
Obtain the last modified date by making GET request to GitHub.
Don't render anything if there's any error with the GET request.
Add tests, and mock the network call.
Closes#1564
Is your feature request related to a problem? Please describe.
When looking at a PEP page on
python.org
, it isn't obvious when the PEP was last modified, or how to see recent revisions.In addition, search engines often aren't displaying useful information. E.g. the Google result for a search of PEPs seems to show the
Created:
date, which may confuse searchers. E.g. the date listed for PEP 518 in a Google search isMay 10, 2016
, though this Provisional PEP was most recently updated onDec 13, 2019
.Describe the solution you'd like
It would be great if the footer of the HTML rendering of each PEP, when served by
python.org
, included aLast-Modified:
date, with a link to the GitHub history for more information. It could go after the Source link at the bottom of the page. E.g.Including relevant dates as metadata such as
datePublished
anddateModified
should help search engines display more helpful information, as described at Official Google Webmaster Central Blog: Help Google Search know the best date for your web pageOur documentation at PEP Page Generation — Python.org Website 1.0 documentation describes the current process.
Given the
peps
git repo obtained via that process, it seems to take less than 20 seconds to get the latest modification date of all the PEPs via e.g. even using the shell pipeline listed at How to retrieve the last modification date of all files in a git repository - Server Fault, so I don't think there would be much overhead to maintaining this information.Describe alternatives you've considered
A discussion of some of the options for making PEP history clearer, or whether version numbers or changelogs for PEPs would be worthwhile, is at Easier tracking of PEP changes, versions, or modification dates - PEPs - Discussions on Python.org. The approach described here expands on what I see as the result of that discussion.
Adding
Last-Modified
information to the PEP 0 page might also be worthwhile, as suggested there.The text was updated successfully, but these errors were encountered: