iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

conflict between alternative proposed syntax and reST markup; escaped with inline literals

This commit is contained in:
David Goodger 2004-04-04 16:19:26 +00:00
parent f25aa6ef73
commit a8380d6616
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
pep-0318.txt
View File

@ -210,14 +210,14 @@ Why [...]?
----------
For syntax options which use a list-like syntax to specify the
decorators a few alternatives have been proposed: '[|...|]',
'*[...]*', and '<...>'. None have gained traction. The alternatives
which involve square brackets only serve to make it obvious that the
decorator construct is not a list. They do nothing to make parsing
any easier. The '<...>' alternative presents parsing problems because
'<' and '>' already parse as un-paired. They present a further
parsing ambiguity because a right angle bracket might be a greater
than symbol instead of a closer for the decorators.
decorators a few alternatives have been proposed: ``[|...|]``,
``*[...]*``, and ``<...>``. None have gained traction. The
alternatives which involve square brackets only serve to make it
obvious that the decorator construct is not a list. They do nothing
to make parsing any easier. The '<...>' alternative presents parsing
problems because '<' and '>' already parse as un-paired. They present
a further parsing ambiguity because a right angle bracket might be a
greater than symbol instead of a closer for the decorators.
Current Implementation