New submission from Zearin:
When exploring the docs for the standard library, it’s frustrating to have an
idea and look for the answer only to find out that an entire module (or
package) has been deprecated _after_ I click on it.
Can we have links to deprecated items on the Standard
Zearin added the comment:
I agree that globally linking all occurrences of True/False/None is overkill.
Perhaps linking the first occurrence per webpage would be a good standard?
However, I *strongly* believe that:
1. The words be capitalized
2. The words should be marked up as ``True
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
> app
Zearin added the comment:
Note: Javascript has something analogous to Python’s ``==`` and ``is``.
In JS:
> 0 == false
true
> 0 === false
false
> 1 == true
true
> 1 === true
false
Perhaps this discrepancy could be fixed in the JSON processing?
--
n
Zearin added the comment:
I recently attempted to enhance the documentation in #17074. While I wasn’t
linking all occurrences of True/False/None, I did mark them up as
``True``/``False``/``None``. Additionally, I made sure that these were (when
appropriate) capitalized.
I really disagree
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
Changes by Zearin :
--
type: -> enhancement
___
Python tracker
<http://bugs.python.org/issue17074>
___
___
Python-bugs-list mailing list
Unsubscri
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
Zearin added the comment:
Does `hg diff` produce different output than regular `diff`?
If so, the patch created by regular `diff` is attached.
(I basically did my work without using a local repo, and I have very little
experience with patching. I basically just looked up how to create a
New submission from Zearin :
Cleaned up the source of the Standard Library’s `cmd` module.
Attempted to focus on readability by changing things like using booleans
instead of 0/1, newer syntax for string formatting, lining up variable
declarations (judgement call), and adding comments
10 matches
Mail list logo
