[issue12101] PEPs should have consecutive revision numbers

Éric Araujo added the comment: This request is not feasible with Mercurial and the useful info is already available. Closing. -- resolution: -> works for me stage: -> committed/rejected status: open -> closed ___ Python tracker

[issue12101] PEPs should have consecutive revision numbers

Éric Araujo added the comment: IOW, invalid? -- components: +None -Devguide nosy: +eric.araujo ___ Python tracker ___ ___ Python-bugs

[issue12101] PEPs should have consecutive revision numbers

Georg Brandl added the comment: The Last-Modified date should tell you just the same, without any arbitrary version numbers that don't have a meaning in hg. And behold, the Last-Modified date already links to the hg page for this PEP, from where you can select the "file log" to get to the lis

[issue12101] PEPs should have consecutive revision numbers

New submission from anatoly techtonik : Currently, PEPs have only hash number, which doesn't explain about how many changes were done to the PEP since my last review. It will be convenient to have consecutive revision number for PEP edits and link it to short history log (like wiki history) wi