<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 30 April 2018 at 18:11, Victor Stinner <span dir="ltr"><<a href="mailto:vstinner@redhat.com" target="_blank">vstinner@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">2018-04-27 17:37 GMT+02:00 Petr Viktorin <<a href="mailto:encukou@gmail.com">encukou@gmail.com</a>>:<br>
> (...)<br>
<span class="gmail-">> - The paragraph about the anticipated future where python points to Python 3<br>
> is removed.<br>
<br>
</span>Instead of editing old PEPs, would it make sense to write a new one<br>
which replaces the old one?<br>
<br>
The PEP 394 has been written in 2011 and accepted in 2012. Editing an<br>
accepted PEP makes it harder to dig into the history of PEPs.<br>
<br>
I know that the PEP 8 is updated regularly, so it's not a requirement,<br>
just a proposal for the special PEP 394.<br></blockquote><div><br></div></div>We edit PEP 394 in place for the same reason we edit PEP 8 in place: so people have a consistent place to get our current recommendations.<br><br></div><div class="gmail_extra">It isn't like a packaging interoperability spec or the Python language & library specs, where folks regularly need to know what changed between particular revisions.<br><br></div><div class="gmail_extra">If folks really want to know how the recommendations have changed over time, then browsing <a href="https://github.com/python/peps/commits/master/pep-0394.txt">https://github.com/python/peps/commits/master/pep-0394.txt</a> isn't overly difficult.<br><br></div><div class="gmail_extra">(That said, I also wouldn't be opposed to adding an inline change log to the PEP, since it helps highlights the cases where the recommendations *have* changed, which can be helpful for folks that were already familiar with the older versions)<br></div><div class="gmail_extra"><br></div><div class="gmail_extra">Cheers,<br></div><div class="gmail_extra">Nick.<br clear="all"></div><div class="gmail_extra"><br>-- <br><div class="gmail_signature">Nick Coghlan   |   <a href="mailto:ncoghlan@gmail.com" target="_blank">ncoghlan@gmail.com</a>   |   Brisbane, Australia</div>
</div></div>