➜

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 taleinat
Recipients Arfrever, Daniel.Garcia, Philippe.Godbout, benjamin.peterson, christian.heimes, edulix, georg.brandl, jcea, jwilk, lars.gustaebel, martin.panter, ned.deily, r.david.murray, serhiy.storchaka, shanxS, taleinat
Date 2018-09-16.14:39:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1537108780.22.0.956365154283.issue21109@psf.upfronthosting.co.za>
In-reply-to
Content 
For one thing, the new diffs are still missing tests.

Tests should include, at the least:

1. *Safely* testing SafeTarFile against examples of problematic tarballs. Perhaps from Jakub's collection of "sly" tarballs could be used, assuming those could be licensed appropriately.
2. SafeTarFile should pass all of the normal TarFile tests.
History
Date User Action Args
2018-09-16 14:39:40taleinatsetrecipients: + taleinat, georg.brandl, jcea, lars.gustaebel, christian.heimes, benjamin.peterson, jwilk, ned.deily, Arfrever, r.david.murray, martin.panter, serhiy.storchaka, edulix, Daniel.Garcia, Philippe.Godbout, shanxS
2018-09-16 14:39:40taleinatsetmessageid: <1537108780.22.0.956365154283.issue21109@psf.upfronthosting.co.za>
2018-09-16 14:39:40taleinatlinkissue21109 messages
2018-09-16 14:39:40taleinatcreate