2.3.9 File Objects
File objects are implemented using C's
package and can be created with the built-in constructor
file() described in section
2.1, ``Built-in Functions.''2.10 File objects are also returned
by some other built-in functions and methods, such as
os.popen() and os.fdopen() and the
makefile() method of socket objects.
When a file operation fails for an I/O-related reason, the exception
IOError is raised. This includes situations where the
operation is not defined for some reason, like seek() on a tty
device or writing a file opened for reading.
Files have the following methods:
Close the file. A closed file cannot be read or written any more.
Any operation which requires that the file be open will raise a
ValueError after the file has been closed. Calling
close() more than once is allowed.
Flush the internal buffer, like
fflush(). This may be a no-op on some file-like
Return the integer ``file descriptor'' that is used by the
underlying implementation to request I/O operations from the
operating system. This can be useful for other, lower level
interfaces that use file descriptors, such as the
fcntl module or
os.read() and friends. Note:
which do not have a real file descriptor should not provide
True if the file is connected to a tty(-like) device, else
If a file-like object is not associated
with a real file, this method should not be implemented.
A file object is its own iterator, for example
f (unless f is closed). When a file is used as an
iterator, typically in a for loop (for example,
for line in f: print line), the next() method is
called repeatedly. This method returns the next input line, or raises
StopIteration when EOF is hit. In order to make a
for loop the most efficient way of looping over the lines of
a file (a very common operation), the next() method uses a
hidden read-ahead buffer. As a consequence of using a read-ahead
buffer, combining next() with other file methods (like
readline()) does not work right. However, using
seek() to reposition the file to an absolute position will
flush the read-ahead buffer.
New in version 2.3.
Read at most size bytes from the file (less if the read hits
EOF before obtaining size bytes). If the size
argument is negative or omitted, read all data until EOF is
reached. The bytes are returned as a string object. An empty
string is returned when EOF is encountered immediately. (For
certain files, like ttys, it makes sense to continue reading after
an EOF is hit.) Note that this method may call the underlying
C function fread() more than once in an effort to
acquire as close to size bytes as possible. Also note that
when in non-blocking mode, less data than what was requested may
be returned, even if no size parameter was given.
Read one entire line from the file. A trailing newline character is
kept in the string (but may be absent when a file ends with an
incomplete line).2.11 If the size argument is present and
non-negative, it is a maximum byte count (including the trailing
newline) and an incomplete line may be returned.
An empty string is returned only when EOF is encountered
stdio's fgets(), the
returned string contains null characters (
'\0') if they
occurred in the input.
Read until EOF using readline() and return a list containing
the lines thus read. If the optional sizehint argument is
present, instead of reading up to EOF, whole lines totalling
approximately sizehint bytes (possibly after rounding up to an
internal buffer size) are read. Objects implementing a file-like
interface may choose to ignore sizehint if it cannot be
implemented, or cannot be implemented efficiently.
This method returns the same thing as
New in version 2.1.
Deprecated since release 2.3.
Use "for line in file" instead.
Set the file's current position, like
The whence argument is optional and defaults to
(absolute file positioning); other values are
relative to the current position) and
2 (seek relative to the
file's end). There is no return value. Note that if the file is
opened for appending (mode
seek() operations will be undone at the next write. If the
file is only opened for writing in append mode (mode
this method is essentially a no-op, but it remains useful for files
opened in append mode with reading enabled (mode
'a+'). If the
file is opened in text mode (mode
't'), only offsets returned
by tell() are legal. Use of other offsets causes undefined
Note that not all file objects are seekable.
Return the file's current position, like
Truncate the file's size. If the optional size argument is
present, the file is truncated to (at most) that size. The size
defaults to the current position. The current file position is
not changed. Note that if a specified size exceeds the file's
current size, the result is platform-dependent: possibilities
include that file may remain unchanged, increase to the specified
size as if zero-filled, or increase to the specified size with
undefined new content.
Availability: Windows, many Unix variants.
Write a string to the file. There is no return value. Due to
buffering, the string may not actually show up in the file until
the flush() or close() method is called.
Write a sequence of strings to the file. The sequence can be any
iterable object producing strings, typically a list of strings.
There is no return value.
(The name is intended to match readlines();
writelines() does not add line separators.)
Files support the iterator protocol. Each iteration returns the same
file.readline(), and iteration ends when the
readline() method returns an empty string.
File objects also offer a number of other interesting attributes.
These are not required for file-like objects, but should be
implemented if they make sense for the particular object.
bool indicating the current state of the file object. This is a
read-only attribute; the close() method changes the value.
It may not be available on all file-like objects.
The encoding that this file uses. When Unicode strings are written
to a file, they will be converted to byte strings using this encoding.
In addition, when the file is connected to a terminal, the attribute
gives the encoding that the terminal is likely to use (that
information might be incorrect if the user has misconfigured the
terminal). The attribute is read-only and may not be present on
all file-like objects. It may also be
None, in which case
the file uses the system default encoding for converting Unicode
New in version 2.3.
The I/O mode for the file. If the file was created using the
open() built-in function, this will be the value of the
mode parameter. This is a read-only attribute and may not be
present on all file-like objects.
If the file object was created using open(), the name of
the file. Otherwise, some string that indicates the source of the
file object, of the form "<...>". This is a read-only
attribute and may not be present on all file-like objects.
If Python was built with the --with-universal-newlines
option to configure (the default) this read-only attribute
exists, and for files opened in
universal newline read mode it keeps track of the types of newlines
encountered while reading the file. The values it can take are
no newlines read yet) or a tuple containing all the newline
types seen, to indicate that multiple
newline conventions were encountered. For files not opened in universal
newline read mode the value of this attribute will be
Boolean that indicates whether a space character needs to be printed
before another value when using the print statement.
Classes that are trying to simulate a file object should also have a
writable softspace attribute, which should be initialized to
zero. This will be automatic for most classes implemented in Python
(care may be needed for objects that override attribute access); types
implemented in C will have to provide a writable
This attribute is not used to control the
print statement, but to allow the implementation of
print to keep track of its internal state.
See About this document... for information on suggesting changes.
- ... Functions.''2.10
is new in Python 2.2. The older built-in open() is an
alias for file().
- ... line).2.11
The advantage of leaving the newline on is that
returning an empty string is then an unambiguous EOF
indication. It is also possible (in cases where it might
matter, for example, if you
want to make an exact copy of a file while scanning its lines)
to tell whether the last line of a file ended in a newline
or not (yes this happens!).