mirror of
https://github.com/python/cpython.git
synced 2025-08-04 17:08:35 +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
|
@ -10,7 +10,14 @@
|
|||
|
||||
This module implements some useful functions on pathnames. To read or
|
||||
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::
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue