mirror of https://github.com/python/cpython
Rewrap.
This commit is contained in:
parent
c166076910
commit
9d9848e776
|
@ -181,22 +181,22 @@ Glossary
|
|||
not expressions.
|
||||
|
||||
extension module
|
||||
A module written in C or C++, using Python's C API to interact with the core and
|
||||
with user code.
|
||||
A module written in C or C++, using Python's C API to interact with the
|
||||
core and with user code.
|
||||
|
||||
file object
|
||||
An object exposing a file-oriented API (with methods such as
|
||||
:meth:`read()` or :meth:`write()`) to an underlying resource.
|
||||
Depending on the way it was created, a file object can mediate access
|
||||
to a real on-disk file or to another other type of storage or
|
||||
communication device (for example standard input/output, in-memory
|
||||
buffers, sockets, pipes, etc.). File objects are also called
|
||||
:dfn:`file-like objects` or :dfn:`streams`.
|
||||
:meth:`read()` or :meth:`write()`) to an underlying resource. Depending
|
||||
on the way it was created, a file object can mediate access to a real
|
||||
on-disk file or to another other type of storage or communication device
|
||||
(for example standard input/output, in-memory buffers, sockets, pipes,
|
||||
etc.). File objects are also called :dfn:`file-like objects` or
|
||||
:dfn:`streams`.
|
||||
|
||||
There are actually three categories of file objects: raw binary
|
||||
files, buffered binary files and text files. Their interfaces are
|
||||
defined in the :mod:`io` module. The canonical way to create a
|
||||
file object is by using the :func:`open` function.
|
||||
There are actually three categories of file objects: raw binary files,
|
||||
buffered binary files and text files. Their interfaces are defined in the
|
||||
:mod:`io` module. The canonical way to create a file object is by using
|
||||
the :func:`open` function.
|
||||
|
||||
file-like object
|
||||
A synonym for :term:`file object`.
|
||||
|
|
Loading…
Reference in New Issue