[issue7357] tarfile doesn't detect disk full error on extraction

2009-12-13 Thread Lars Gustäbel

Lars Gustäbel l...@gustaebel.de added the comment:

I changed the default value for the errorlevel argument, so that fatal
errors are now raised as regular exceptions by default (trunk: r76780,
py3k: r76782). Thank you very much for bringing up this issue.

--
resolution:  - accepted
status: open - closed
type:  - behavior

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7357
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue7357] tarfile doesn't detect disk full error on extraction

2009-11-20 Thread Eli Venter

Eli Venter even...@jcvi.org added the comment:

Yes, thanks errorlevel works as expected, and errors are correctly
generated. It's quite unintuitive to ignore fatal errors by default
however.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7357
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue7357] tarfile doesn't detect disk full error on extraction

2009-11-19 Thread Eli Venter

New submission from Eli Venter even...@jcvi.org:

tarfile doesn't seem to return any error or raise any exception when an
extraction fills up the disk, making it hard to use safely. Both
extractall and extract suffer from this problem. I'm using CentOS 5.2
and python 2.6.2.

--
components: Library (Lib)
messages: 95481
nosy: eliv
severity: normal
status: open
title: tarfile doesn't detect disk full error on extraction
versions: Python 2.6

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7357
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue7357] tarfile doesn't detect disk full error on extraction

2009-11-19 Thread Lars Gustäbel

Lars Gustäbel l...@gustaebel.de added the comment:

The TarFile constructor (as well as tarfile.open) takes an errorlevel
keyword argument. See
http://docs.python.org/dev/library/tarfile.html#tarfile-objects

I quote: If errorlevel is 0, all errors are ignored when using
TarFile.extract(). Nevertheless, they appear as error messages in the
debug output, when debugging is enabled. If 1, all fatal errors are
raised as OSError or IOError exceptions. If 2, all non-fatal errors are
raised as TarError exceptions as well.

Hope that helps.

--
assignee:  - lars.gustaebel
nosy: +lars.gustaebel

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7357
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com