Martin Panter added the comment:
Hoping my clarification in the documentation is enough to call this fixed
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
versions: +Python 2.7, Python 3.6 -Python 3.4
___
Python
Roundup Robot added the comment:
New changeset 94a94deaf06a by Martin Panter in branch '3.5':
Issues #22468, #21996, #22208: Clarify gettarinfo() and TarInfo usage
https://hg.python.org/cpython/rev/94a94deaf06a
New changeset e66c476b25ec by Martin Panter in branch 'default':
Issue #22468: Merge
Martin Panter added the comment:
I am posting a documentation patch which I hope should clarify that objects
like GzipFile won’t work automatically with gettarinfo(). It also has other
modifications to address Issue 21996 (name must be text) and help with Issue
22208 (clarify non-OS files
Mark Lawrence added the comment:
msg227328 states it's not a really common scenario but I believe we must
still allow for it, what do others think?
--
nosy: +BreamoreBoy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22468
Martin Panter added the comment:
I think a warning in the documentation might be helpful.
However a special check in the code doesn’t seem right. Would you check for
LZMAFile and BZ2File as well? Some of the other attributes (modification time,
owner, etc) may be useful even for a GzipFile,
New submission from Bart Olsthoorn:
CPython tarfile `gettarinfo` method uses fstat to determine the size of a file
(using its fileobject). When that file object is actually created with
Gzip.open (so a GZipfile), it will get the compressed size of the file. The
addfile method will then
Changes by Ned Deily n...@acm.org:
--
nosy: +lars.gustaebel
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22468
___
___
Python-bugs-list mailing
