From: Lars Gustäbel Date: Mon, 12 Feb 2007 09:25:53 +0000 (+0000) Subject: Bug #1656581: Point out that external file objects are supposed to be X-Git-Tag: v2.6a1~2186 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=a69aa327aaac8c9156d67b16a81d6b082ba5b012;p=python Bug #1656581: Point out that external file objects are supposed to be at position 0. --- diff --git a/Doc/lib/libtarfile.tex b/Doc/lib/libtarfile.tex index 1a53a27e76..96f835f539 100644 --- a/Doc/lib/libtarfile.tex +++ b/Doc/lib/libtarfile.tex @@ -49,8 +49,8 @@ Some facts and figures: avoid this. If a compression method is not supported, \exception{CompressionError} is raised. - If \var{fileobj} is specified, it is used as an alternative to - a file object opened for \var{name}. + If \var{fileobj} is specified, it is used as an alternative to a file + object opened for \var{name}. It is supposed to be at position 0. For special purposes, there is a second format for \var{mode}: \code{'filemode|[compression]'}. \function{open()} will return a @@ -161,6 +161,7 @@ tar archive several times. Each archive member is represented by a If \var{fileobj} is given, it is used for reading or writing data. If it can be determined, \var{mode} is overridden by \var{fileobj}'s mode. + \var{fileobj} will be used from position 0. \begin{notice} \var{fileobj} is not closed, when \class{TarFile} is closed. \end{notice}