[issue21972] Bugs in the lexer and parser documentation

Changes by Martin v. Löwis : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue21972] Bugs in the lexer and parser documentation

Martin v. Löwis added the comment: I've moved the @ operator into #22142. With that, it seems to me that all aspects of this report are resolved. François-René, for the future, please submit an individual bug report for each independent issue; this makes it easier tracking what has and hasn't

[issue21972] Bugs in the lexer and parser documentation

Roundup Robot added the comment: New changeset 57740d19f5c2 by Martin v. Löwis in branch 'default': Issue #21972: Make it clear that the PEP 401 future import works, http://hg.python.org/cpython/rev/57740d19f5c2 -- nosy: +python-dev ___ Python tracker

[issue21972] Bugs in the lexer and parser documentation

Martin v. Löwis added the comment: The PEP 401 joke actually works: >>> from __future__ import barry_as_FLUFL >>> 3<>4 True I'll add a smiley -- ___ Python tracker ___

[issue21972] Bugs in the lexer and parser documentation

Martin v. Löwis added the comment: The ellipsis is also mentioned: "A sequence of three periods has a special meaning as an ellipsis literal." -- ___ Python tracker ___

[issue21972] Bugs in the lexer and parser documentation

Changes by Ezio Melotti : -- nosy: +benjamin.peterson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://m

[issue21972] Bugs in the lexer and parser documentation

François-René Rideau added the comment: Actually, my reading was buggy, and the "u" part is well-documented enough. Apologies for this part of the bug report. The lexer documentation is still missing the ellipsis, though Other bug I found in the lexer documentation: missing @= And the parser

[issue21972] Bugs in the lexer and parser documentation

Martin v. Löwis added the comment: I don't understand. It says "it is possible again to prefix unicode strings with a u prefix" which seems to include both what ("prefix unicode strings") and how ("with a u prefix"). Can you propose specific wording that you want to see included? -- n

[issue21972] Bugs in the lexer and parser documentation

New submission from François-René Rideau: The lexer documentation says that the u prefix works on strings since 3.3, but doesn't explain what or how, which is all the more problematic since it explicitly mentions difference from the behavior documented in Python 2. It also doesn't specify the