Convert text-based PEPs to reST

[brettcannon]

Not really important, but it does unify things.

[Carreau]

Stupid existential question, should pep-9 (Sample Plaintext PEP Template) be converted to rst ?

[Rosuav]

Haha, good question. Maybe keep it as text and identify it as deprecated?

[Carreau]

Haha, good question. Maybe keep it as text and identify it as deprecated?

It is already. But if not converted, that would make it trickier to automatize the Sphinx build process.

One possibility is to put the all content of the pep in code block. Indented by 4 spaces, and add an warning on top.

[brettcannon]

That's a possibility. I would leave that PEP for last for conversion as it's obviously the least important one to convert.

[brettcannon]

#142, #143, #144, and #148 are conversions from text to reST.

[Mariatta]

Not including PEP 9, there are 133 more PEPs still in plain text :P

[gvanrossum]

So my strategy would be to take each next conversion as an opportunity to refine your conversion script. After 33 improvements the rest should not need manual tweaking.

[brettcannon]

Once you're comfortable that your script isn't going to break anything, @Mariatta , then I would be fine with one big PR or batches of PRs that converts several of the text-only PEPs at once. We have version control for a reason. 😄

[Carreau]

For the few peps I made into rst I used this, if it can be of help. I found that a couple of peps/peps author were using different style and the you regularly need to make manual check/fixes after auto transform.