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
b2afc811
Commit
b2afc811
authored
Aug 29, 1997
by
Guido van Rossum
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Added os.altsep; this is '/' on DOS/Windows, and None on systems with
a sane filename syntax.
parent
a28dab5e
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
16 additions
and
4 deletions
+16
-4
Doc/lib/libos.tex
Doc/lib/libos.tex
+8
-2
Doc/libos.tex
Doc/libos.tex
+8
-2
No files found.
Doc/lib/libos.tex
View file @
b2afc811
...
@@ -52,13 +52,19 @@ e.g. \code{'..'} for POSIX or \code{'::'} for the Mac.
...
@@ -52,13 +52,19 @@ e.g. \code{'..'} for POSIX or \code{'::'} for the Mac.
\end{datadesc}
\end{datadesc}
\begin{datadesc}
{
sep
}
\begin{datadesc}
{
sep
}
The character used by the OS to separate pathname components,
e.g.
\
The character used by the OS to separate pathname components,
\code
{
'/'
}
for POSIX or
\code
{
':'
}
for the Mac. Note that knowing this
e.g.
\code
{
'/'
}
for POSIX or
\code
{
':'
}
for the Mac. Note that knowing this
is not sufficient to be able to parse or concatenate pathnames---better
is not sufficient to be able to parse or concatenate pathnames---better
use
\code
{
os.path.split()
}
and
\code
{
os.path.join()
}
---but it is
use
\code
{
os.path.split()
}
and
\code
{
os.path.join()
}
---but it is
occasionally useful.
occasionally useful.
\end{datadesc}
\end{datadesc}
\begin{datadesc}
{
altsep
}
An alternative character used by the OS to separate pathname components,
or
\code
{
None
}
if only one separator character exists. This is set to
\code
{
'/'
}
on DOS/Windows systems where
\code
{
sep
}
is a backslash.
\end{datadesc}
\begin{datadesc}
{
pathsep
}
\begin{datadesc}
{
pathsep
}
The character conventionally used by the OS to separate search patch
The character conventionally used by the OS to separate search patch
components (as in
\code
{
\$
PATH
}
), e.g.
\ \code
{
':'
}
for POSIX or
components (as in
\code
{
\$
PATH
}
), e.g.
\ \code
{
':'
}
for POSIX or
...
...
Doc/libos.tex
View file @
b2afc811
...
@@ -52,13 +52,19 @@ e.g. \code{'..'} for POSIX or \code{'::'} for the Mac.
...
@@ -52,13 +52,19 @@ e.g. \code{'..'} for POSIX or \code{'::'} for the Mac.
\end{datadesc}
\end{datadesc}
\begin{datadesc}
{
sep
}
\begin{datadesc}
{
sep
}
The character used by the OS to separate pathname components,
e.g.
\
The character used by the OS to separate pathname components,
\code
{
'/'
}
for POSIX or
\code
{
':'
}
for the Mac. Note that knowing this
e.g.
\code
{
'/'
}
for POSIX or
\code
{
':'
}
for the Mac. Note that knowing this
is not sufficient to be able to parse or concatenate pathnames---better
is not sufficient to be able to parse or concatenate pathnames---better
use
\code
{
os.path.split()
}
and
\code
{
os.path.join()
}
---but it is
use
\code
{
os.path.split()
}
and
\code
{
os.path.join()
}
---but it is
occasionally useful.
occasionally useful.
\end{datadesc}
\end{datadesc}
\begin{datadesc}
{
altsep
}
An alternative character used by the OS to separate pathname components,
or
\code
{
None
}
if only one separator character exists. This is set to
\code
{
'/'
}
on DOS/Windows systems where
\code
{
sep
}
is a backslash.
\end{datadesc}
\begin{datadesc}
{
pathsep
}
\begin{datadesc}
{
pathsep
}
The character conventionally used by the OS to separate search patch
The character conventionally used by the OS to separate search patch
components (as in
\code
{
\$
PATH
}
), e.g.
\ \code
{
':'
}
for POSIX or
components (as in
\code
{
\$
PATH
}
), e.g.
\ \code
{
':'
}
for POSIX or
...
...
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
