\begin{methoddesc}[file]{isatty}{}

Return \code{True} if the file is connected to a tty(-like) device, else

\code{False}. \note{If a file-like object is not associated

with a real file, this method should \emph{not} be implemented.}

\end{methoddesc}

\begin{methoddesc}[file]{next}{}

A file object is its own iterator, i.e. \code{iter(\var{f})} returns

\var{f} (unless \var{f} is closed). When a file is used as an

iterator, typically in a \keyword{for} loop (for example,

\code{for line in f: print line}), the \method{next()} method is

called repeatedly. This method returns the next input line, or raises

\exception{StopIteration} when \EOF{} is hit. In order to make a

\keyword{for} loop the most efficient way of looping over the lines of

a file (a very common operation), the \method{next()} method uses a

hidden read-ahead buffer. As a consequence of using a read-ahead

buffer, combining \method{next()} with other file methods (like

\method{readline()}) does not work right. However, using

\method{seek()} to reposition the file to an absolute position will

flush the read-ahead buffer.

\versionadded{2.3}

\end{methoddesc}

This method returns the same thing as \code{iter(f)}.

\deprecated{2.3}{Use \code{for line in file} instead.}