Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
cpython
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
cpython
Commits
c5207c84
Commit
c5207c84
authored
May 11, 2007
by
Georg Brandl
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Patch #1714700: clarify os.linesep vs. tfiles opened in text mode.
(backport)
parent
bc1b5f16
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
6 additions
and
3 deletions
+6
-3
Doc/lib/libos.tex
Doc/lib/libos.tex
+6
-3
No files found.
Doc/lib/libos.tex
View file @
c5207c84
...
...
@@ -2009,9 +2009,12 @@ Also available via \module{os.path}.
\begin{datadesc}
{
linesep
}
The string used to separate (or, rather, terminate) lines on the
current platform. This may be a single character, such as
\code
{
'
\e
n'
}
for
\POSIX
{}
or
\code
{
'
\e
r'
}
for Mac OS, or multiple characters,
for example,
\code
{
'
\e
r
\e
n'
}
for Windows.
current platform. This may be a single character, such as
\code
{
'
\e
n'
}
for
\POSIX
{}
or
\code
{
'
\e
r'
}
for Mac OS, or multiple
characters, for example,
\code
{
'
\e
r
\e
n'
}
for Windows.
Do not use
\var
{
os.linesep
}
as a line terminator when writing files
opened in text mode (the default); use a single
\code
{
'
\e
n'
}
instead,
on all platforms.
\end{datadesc}
\begin{datadesc}
{
devnull
}
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment