This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Title: Odd formatting differences of keywords in reference
Type: behavior Stage: needs patch
Components: Documentation Versions: Python 3.0, Python 3.1
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: georg.brandl Nosy List: MLModel, georg.brandl, r.david.murray
Priority: normal Keywords:

Created on 2009-05-04 19:12 by MLModel, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (6)
msg87153 - (view) Author: Mitchell Model (MLModel) Date: 2009-05-04 19:12
In the section at reference/lexical_analysis.html#keywords of the HTML
documentation some of the keywords are formatted differently from the
majority. In the HTML markup most of the keywords have CSS class 'k',
but others have 'n', 'nc', 'kn', 'nn', or 'ow'. I don't see any pattern
to which keywords are formatted which way, so I believe this should be
corrected. Or, if the differences are intentional they should be
documented. [Just trying to help clean up the doc -- I realize how
trivial this is.]
msg87159 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2009-05-04 19:51
Whare are you seeing this?  The online documentation doesn't use css
class names like the ones you mention as far as I can see.
msg87160 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2009-05-04 19:53
Woops, I was looking at the wrong page.  I see it now.
msg87162 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2009-05-04 20:10
It looks like the py3 table is being colorized incorrectly.  The rst
source code looks the same, so it must be some sort of difference in
configuration.  I think I'll leave it to Georg to sort out :)
msg87163 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2009-05-04 20:14
A thought: there are additional keywords words in the Py3 table. 
Perhaps Sphinx is using a heuristic to detect example blocks that are
python source code, and this one does not qualify in the py2 docs but
does qualify in the p3 docs.  In the py2 docs the table is not colorized
at all.
msg87167 - (view) Author: Georg Brandl (georg.brandl) * (Python committer) Date: 2009-05-04 20:42
Pygments' cleverness is detrimental here.  It highlights module, class
and function names specially, therefore the identifiers after "class"
and "import" are differently colored.

I've made the table non-highlighted in 2 and 3, r72288.
Date User Action Args
2022-04-11 14:56:48adminsetgithub: 50175
2009-05-04 20:42:37georg.brandlsetstatus: open -> closed
resolution: fixed
messages: + msg87167
2009-05-04 20:14:09r.david.murraysetmessages: + msg87163
2009-05-04 20:10:05r.david.murraysettype: behavior
messages: + msg87162
stage: needs patch
2009-05-04 19:53:25r.david.murraysetmessages: + msg87160
2009-05-04 19:51:08r.david.murraysetnosy: + r.david.murray
messages: + msg87159
2009-05-04 19:12:05MLModelcreate