[issue16631] tarfile.extractall() doesn't extract everything if .next() was used

Serhiy Storchaka added the comment: Patch for issue16601 has fixed this issue too. -- resolution: -> duplicate stage: patch review -> committed/rejected status: open -> closed superseder: -> Restarting iteration over tarfile continues from where it left off. _

[issue16631] tarfile.extractall() doesn't extract everything if .next() was used

Changes by Serhiy Storchaka : -- assignee: -> serhiy.storchaka versions: -Python 3.2 ___ Python tracker ___ ___ Python-bugs-list mai

[issue16631] tarfile.extractall() doesn't extract everything if .next() was used

anatoly techtonik added the comment: Ping. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue16631] tarfile.extractall() doesn't extract everything if .next() was used

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue16631] tarfile.extractall() doesn't extract everything if .next() was used

Changes by Jesús Cea Avión : -- nosy: +jcea ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue16631] tarfile.extractall() doesn't extract everything if .next() was used

Serhiy Storchaka added the comment: Since you iterated to the end any iterators are independent (they are just indices in the list of members). -- ___ Python tracker ___ ___

[issue16631] tarfile.extractall() doesn't extract everything if .next() was used

R. David Murray added the comment: I wonder if both bugs are symptoms of an underlying bug: if you call 'iter' twice on a tarfile, are the iterators independent? Is that even a sensible thing to be able to do? -- nosy: +r.david.murray ___ Python tr

[issue16631] tarfile.extractall() doesn't extract everything if .next() was used

Serhiy Storchaka added the comment: OK. Then those issues are just related. -- nosy: +lars.gustaebel stage: -> patch review type: -> behavior ___ Python tracker ___ ___

[issue16631] tarfile.extractall() doesn't extract everything if .next() was used

anatoly techtonik added the comment: issue16601 is about restarting iterations from zero if interrupted. This one is that extractall() should not use public iteration API at all. -- ___ Python tracker

[issue16631] tarfile.extractall() doesn't extract everything if .next() was used

Serhiy Storchaka added the comment: Possible this is a duplicate of issue16601. -- nosy: +serhiy.storchaka versions: -Python 3.1 ___ Python tracker ___ _

[issue16631] tarfile.extractall() doesn't extract everything if .next() was used

anatoly techtonik added the comment: Attached is patch with test. Test needs valid extractable .tar file. The testtar.tar that is currently present fails to unpack on Windows because of too long filenames inside. -- keywords: +patch Added file: http://bugs.python.org/file28232/16631.pa

[issue16631] tarfile.extractall() doesn't extract everything if .next() was used

New submission from anatoly techtonik: If tarfile.next() is used before .extractall(), the latter fails to extract files that were accessed. -- components: Library (Lib) messages: 177065 nosy: techtonik priority: normal severity: normal status: open title: tarfile.extractall() doesn't e