# Easier tracking of PEP changes, versions, or modification dates **URL:** \ **Category:** PEPs\ **Tags:** git\ **Created:** [March 6, 2020, 6:00pm UTC](https://discuss.python.org/t/easier-tracking-of-pep-changes-versions-or-modification-dates/3658 "2020-03-06T18:00:53Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![nealmcb](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/nealmcb/32/869_2.png) [@nealmcb](https://discuss.python.org/u/nealmcb)\ **Post date:** [March 6, 2020, 7:26pm UTC](https://discuss.python.org/t/easier-tracking-of-pep-changes-versions-or-modification-dates/3658/3 "2020-03-06T19:26:34Z")
> [@brettcannon](#): > > Could you say _why_ you want this? The PEP process is decades old at this point and we have not felt the need for versioning, so I would like to understand what your specific use-case is before we start considering changing software and/or processes to accommodate it. Indeed - happy to say why, and thanks for the answers. I’ve looked at a variety of PEPs over time, and was surprised to discover that there were changes which I had missed. I’m used to other standardization practices, which do track versions or timestamps, and I had no idea that PEPs were changing without any obvious visible indication other than reading the whole thing or following links. I assumed that `Post-History` was an indication of when the PEP changed, i.e. when it was posted to the web site. I don’t want to have to follow links just to know if there have been changes recently. A `Last-modified` date is pretty common on web sites and seems like it would be a straightforward addition which would help engage people more effectively and productively. --- _[View the full topic](https://discuss.python.org/t/easier-tracking-of-pep-changes-versions-or-modification-dates/3658)._