mirror of
https://github.com/python/cpython.git
synced 2025-09-26 18:29:57 +00:00
More bytes vs. strings documentation.
This commit is contained in:
parent
a731b9929f
commit
651423c1eb
3 changed files with 15 additions and 5 deletions
|
@ -710,10 +710,11 @@ are always available. They are listed here in alphabetical order.
|
||||||
|
|
||||||
Open a file. If the file cannot be opened, :exc:`IOError` is raised.
|
Open a file. If the file cannot be opened, :exc:`IOError` is raised.
|
||||||
|
|
||||||
*file* is either a string giving the name (and the path if the file isn't in
|
*file* is either a string or bytes object giving the name (and the
|
||||||
the current working directory) of the file to be opened or an integer file
|
path if the file isn't in the current working directory) of the
|
||||||
descriptor of the file to be wrapped. (If a file descriptor is given, it is
|
file to be opened or an integer file descriptor of the file to be
|
||||||
closed when the returned I/O object is closed, unless *closefd* is set to
|
wrapped. (If a file descriptor is given, it is closed when the
|
||||||
|
returned I/O object is closed, unless *closefd* is set to
|
||||||
``False``.)
|
``False``.)
|
||||||
|
|
||||||
*mode* is an optional string that specifies the mode in which the file is
|
*mode* is an optional string that specifies the mode in which the file is
|
||||||
|
|
|
@ -10,7 +10,14 @@
|
||||||
|
|
||||||
This module implements some useful functions on pathnames. To read or
|
This module implements some useful functions on pathnames. To read or
|
||||||
write files see :func:`open`, and for accessing the filesystem see the
|
write files see :func:`open`, and for accessing the filesystem see the
|
||||||
:mod:`os` module.
|
:mod:`os` module. The path parameters can be passed as either strings,
|
||||||
|
or bytes. Applications are encouraged to represent file names as
|
||||||
|
(Unicode) character strings. Unfortunately, some file names may not be
|
||||||
|
representable as strings on Unix, so applications that need to support
|
||||||
|
arbitrary file names on Unix should use bytes objects to represent
|
||||||
|
path names. Vice versa, using bytes objects cannot represent all file
|
||||||
|
names on Windows (in the standard ``mbcs`` encoding), hence Windows
|
||||||
|
applications should use string objects to access all files.
|
||||||
|
|
||||||
.. warning::
|
.. warning::
|
||||||
|
|
||||||
|
|
|
@ -694,6 +694,8 @@ Files and Directories
|
||||||
.. function:: getcwd()
|
.. function:: getcwd()
|
||||||
|
|
||||||
Return a string representing the current working directory.
|
Return a string representing the current working directory.
|
||||||
|
May raise UnicodeDecodeError if the current directory path fails
|
||||||
|
to decode in the file system encoding.
|
||||||
Availability: Unix, Windows.
|
Availability: Unix, Windows.
|
||||||
|
|
||||||
|
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue