➜

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.

classification
Title: Line ending documentation is misleading
Type: Stage:
Components: Documentation Versions: Python 2.4
process
Status: closed Resolution: accepted
Dependencies: Superseder:
Assigned To: fdrake Nosy List: fdrake, paul.moore
Priority: normal Keywords:

Created on 2005-03-21 22:06 by paul.moore, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
ref2.diff paul.moore, 2005-03-21 22:07
Messages (2)
msg24745 - (view) Author: Paul Moore (paul.moore) * (Python committer) Date: 2005-03-21 22:06 
The documentation of line ending conventions is
misleading when embedding Python.

The only documentation I can find on line endings is in
the language reference - section 2.1.2 "Physical
Lines". This describes a physical line as being
terminated with the platform line terminator.

When referring to source files, this is wrong, as
universal newline support now means that any of CR, LF,
or CRLF is a valid line terminator on all platforms.
When embedding (via something like PyRun_SimpleString)
a C-level newline terminator (ie, "\n") is the line
terminator.

I attach a suggested patch to the ref\ref2.tex
documentation file (patch against CVS HEAD as at 29th Jan).
msg24746 - (view) Author: Fred Drake (fdrake) (Python committer) Date: 2005-05-25 05:46 
Logged In: YES 
user_id=3066

Fixed in Doc/ref/ref2.tex revisions 1.57, 1.56.2.1, using
the attached patch.
History
Date User Action Args
2022-04-11 14:56:10adminsetgithub: 41739
2005-03-21 22:06:59paul.moorecreate