On Thu, Dec 27, 2012 at 12:25 PM, Ian Kelly wrote:
> You're correct that it makes no sense to open a tar file in binary
> mode,
Of course that should have read: "it makes no sense to open a tar file
in text mode."
--
http://mail.python.org/mailman/listinfo/python-list
On Thu, Dec 27, 2012 at 11:50 AM, Steven W. Orr wrote:
> Really? I thought that the whole idea of using "rb" or "wb" was something
> that was necessitated by WinBlo$e. We're not doing IO on a text file here.
> It's a tar file which by definition is binary and it's not clear to me why
> unicode has
On 12/26/2012 11:11 AM, Benjamin Kaplan wrote:
On Dec 26, 2012 11:00 AM, "Antoon Pardon" mailto:antoon.par...@rece.vub.ac.be>> wrote:
>
> I am converting some programs to python 3. These programs manipulate
tarfiles. In order for the python3 programs to be really useful
> they need to be able
On Dec 26, 2012 11:00 AM, "Antoon Pardon"
wrote:
>
> I am converting some programs to python 3. These programs manipulate
tarfiles. In order for the python3 programs to be really useful
> they need to be able to process the tarfiles produced by python2 that
however seems to be a problem.
>
> This
You probably want to write
of = open("DUMP.tbz", "wb")
and
gf =open("DUMP.tbz", "rb")
--
http://mail.python.org/mailman/listinfo/python-list
I am converting some programs to python 3. These programs manipulate
tarfiles. In order for the python3 programs to be really useful
they need to be able to process the tarfiles produced by python2 that
however seems to be a problem.
This is testcode that produces a tarfile.
#! /usr/bin/python
