I disagree. PEPs are edited by the same people and in the same editing environments as code, so having such a limit makes it more compatible across disparate editing environments. E.g. lines which are too long can be autowrapped or syntax highlighted in a warning color.

TBH, it also always bothers me when I see Python documentation source files with too long lines.

I agree with Barry; I write PEPs in code editors for their reST support and so the lack of line breaks doesn't work. Plus I personally read plenty of PEPs in raw text form.

I think two PEP editors not in favour of the idea is enough to close this.

i don’t get it, all editors support autowrap, right?

Stop it. It's not going to change. (And no, autowrap isn't always on and doesn't always do the right thing.)

how can it do the wrong thing, though?

If you wrap hard at the column limit with hyphens to get a justified look that can break words at bad points.

But it really doesn't matter as we are not changing this requirement/practice for other reasons as well (e.g. not requiring everyone to turn on auto-wrap), so please consider this issue closed.