New submission from Zearin:
When reading the docs, I noticed that the capitalization and formatting of the
Python constants ``True``, ``False``, and ``None`` were inconsistent.
The attached patch contains a fix for all such occurrences under
``/Doc/library/``.
(I **think** I correctly made
Changes by Zearin zea...@users.sourceforge.net:
--
type: - enhancement
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17074
___
___
Chris Jerdonek added the comment:
This has already been proposed in issue 15580. By the way, you don't always
want to replace true with ``True``. The former has a different
connotation/meaning which is boolean true rather than the object True.
--
nosy: +chris.jerdonek
resolution: -
Zearin added the comment:
Ah; I did look for dupes, but didn’t find it. (So many issues…!)
Thanks for pointing me in the right direction.
By the way, you don't always want to replace true with ``True``.
The former has a different connotation/meaning which is boolean true =
rather than the
Chris Jerdonek added the comment:
Yes, I know. I went through all the occurrences one by one, and I tried to
take that into account.
See issue 4945 for a discussion like this. Might be relevant to what you have
in mind.
--
___
Python tracker
Chris Jerdonek added the comment:
This has already been proposed in issue 15580.
By the way, I should have said something along the same lines. Issue 15580
is about eliminating uses of :const:`None`, etc, whereas this targets a
different case. But it is similar in scope so the same
Zearin added the comment:
By the way, I should have said something along the same lines. Issue 15580
is about eliminating uses of :const:`None`, etc, whereas this targets a
different case. But it is similar in scope so the same discussion/reasons
apply.
Yep! I read, and understood the
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17074
___
___
