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 | lars.gustaebel, loewis, zooko |
| Date | 2008年05月31日.11:06:53 |
| SpamBayes Score | 0.18525288 |
| Marked as misclassified | No |
| Message-id | <1212232018.28.0.113197477711.issue3016@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
With some effort I could reproduce the problem (on a FAT32 filesystem), but what we have here is clearly a usage problem. In unpack_tarfile() in setuptools/archive_util.py TarFile's internal _extract_member() method is used to extract the contents. For every non-fatal error (like a failing chmod()) _extract_member() raises an ExtractError exception. In TarFile.extract() these ExtractErrors are normally ignored. The unpack_tarfile() function in setuptools needs some fixing, it should either act more like TarFile.extract() or better use the public API. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年05月31日 11:06:58 | lars.gustaebel | set | spambayes_score: 0.185253 -> 0.18525288 recipients: + lars.gustaebel, loewis, zooko |
| 2008年05月31日 11:06:58 | lars.gustaebel | set | spambayes_score: 0.185253 -> 0.185253 messageid: <1212232018.28.0.113197477711.issue3016@psf.upfronthosting.co.za> |
| 2008年05月31日 11:06:54 | lars.gustaebel | link | issue3016 messages |
| 2008年05月31日 11:06:53 | lars.gustaebel | create | |