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: PEP 305: eaten backslashes
Type: enhancement Stage: resolved
Components: Documentation Versions:
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: ezio.melotti Nosy List: docs@python, ezio.melotti, pitrou, serhiy.storchaka
Priority: normal Keywords: patch

Created on 2012-11-18 17:33 by serhiy.storchaka, last changed 2022-04-11 14:57 by admin. This issue is now closed.

File name Uploaded Description Edit
pep-0305_rn.patch serhiy.storchaka, 2012-11-18 17:33
Messages (3)
msg175891 - (view) Author: Serhiy Storchaka (serhiy.storchaka) * (Python committer) Date: 2012-11-18 17:33
In PEP 305 '\r\n' rendered as 'rn' in one place.  The proposed patch should fix this.
msg175893 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2012-11-18 17:35
Hmm, I wonder if this is a ReST bug.
msg175898 - (view) Author: Serhiy Storchaka (serhiy.storchaka) * (Python committer) Date: 2012-11-18 17:49
This is a markup bug. In all other cases \n escaped (\\n), or quoted (``\n``), or used in a code fragment.
Date User Action Args
2022-04-11 14:57:38adminsetgithub: 60706
2012-11-18 17:55:47ezio.melottisetstatus: open -> closed

type: enhancement
assignee: docs@python -> ezio.melotti
nosy: + ezio.melotti
resolution: fixed
stage: patch review -> resolved
2012-11-18 17:49:55serhiy.storchakasetmessages: + msg175898
2012-11-18 17:35:04pitrousetnosy: + pitrou
messages: + msg175893
2012-11-18 17:33:29serhiy.storchakacreate