Michael K Johnson added the comment:
The test case at the top of this issue reproduces just fine; if you are
looking for a different test case you'll have to specify what you don't
like about it so that it's clear what you are looking for.
I don't think there's any mys
Michael K Johnson added the comment:
I also ran into this issue, and dealt with it as suggested here by
changing to sets. Because I have underlying code that has to deal both
with small hand-crafted regular expressions and arbitrarily-large
machine-generated sets of paths, I subclassed set and
Michael K Johnson added the comment:
OK, not intended for "everyday use"; I understand this as meaning that
it is considered primarily an internal interface, and thus one that has
an explicitly unstable API. It is hard for me to guess that this would
be the case, since this int
Michael K Johnson added the comment:
We are doing output, and mode='w|' works. We were using
tarfile.TarFile, not realizing that the default constructor was an
unsupported and deprecated interface (!?!)
--
status: open -> closed
___
P
New submission from Michael K Johnson :
In python 2.6 (not 2.4, haven't checked 2.5), the __init__() method of
the TarFile class calls the tell() method on the tar file, which doesn't
work if you are reading from standard input or writing to standard
output, two very reasonable things
