[docs] [issue15580] fix True/False/None reST markup

[Georg Brandl]

Georg Brandl added the comment:

We have to draw the line somewhere.  Otherwise there will be dozens of issues like this, introducing potential breakage and costing developer time that can better be spent elsewhere.

The rule in the devguide is mostly there so that developers don't bother writing more than they have to (since None/True/False occur so often typing the link every time will feel painful after a few times).  If the link is already written, it does absolutely no harm, as David said.  Therefore, there is no actual improvement as you claim.

This is nothing against you and your efforts, Chris -- you've already helped improve the docs quite a lot.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue15580>
_______________________________________