What is recommended in PEP 8, you are engouraged to follow that; not you
as a Python coder but you as a member of the Python community where PEP
8 is the coding style specification. Python's built-in modules have such
a lovely coding style because they all follow PEP 8. Why must the
documentation be an exception not to follow PEP 8? Is there a technical
reason? And the lack of space is not an issue. PEP 8 makes it clear to
"use spaces around arithmetic operators" and then it gives some examples
what is acceptable and what is not. Let us look at this again, shall we?

    Yes:
        i = i + 1
    No:
        i=i+1


Let us convert this into our version from the example code:

    Yes:
        a, b = b, a + b
    No:
        a,b=b,a+b

Only the a+b part is not written according to PEP 8. Python beginners
don't start learning the language by first reading PEP 8. They don't
even know it exists; and since they are beginners, talking about the
coding style is too soon. What they do first is read the Python tutorial
and they look at how code is written in the tutorial and get used to
that. And so if the code is badly written there, they will also write
bad code (bad as in 'with a bad coding style'). So we must set an
example for Python beginners (and also other people) to write
good-coding-style code. So my point is that people won't need to read
PEP 8 if that is applied into the documentation (especially the
tutorial); they'll just look at some example code and know how to write
code. Please fix those things like  a+b to a + b  and  n//x to n // x.

I have added mister van Rossum into this issue report, because I think
we need a BDFL opinion. What do you think, mister van Rossum, about this?