This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author lars.gustaebel
Recipients brian.curtin, eric.araujo, ezio.melotti, jaime.buelta, lars.gustaebel, meador.inge, r.david.murray
Date 2010-02-28.21:05:23
SpamBayes Score 0.00026912635
Marked as misclassified No
Message-id <>
I found an issue that needs to be addressed: if there is an error while the TarFile object is opened for writing, we cannot simply call TarFile.close() in the __exit__() method. close() would try to finalize the archive, i.e. write two zero end-of-archive blocks and a number of padding blocks.

I changed __exit__() to call close() only if everything went fine. If there was an exception only the most basic cleanup is done.

I added more tests and adapted the docs.
Date User Action Args
2010-02-28 21:05:27lars.gustaebelsetrecipients: + lars.gustaebel, ezio.melotti, eric.araujo, r.david.murray, brian.curtin, meador.inge, jaime.buelta
2010-02-28 21:05:27lars.gustaebelsetmessageid: <>
2010-02-28 21:05:25lars.gustaebellinkissue7232 messages
2010-02-28 21:05:25lars.gustaebelcreate