summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorLars Gustäbel <lars@gustaebel.de>2009-12-13 11:43:59 (GMT)
committerLars Gustäbel <lars@gustaebel.de>2009-12-13 11:43:59 (GMT)
commitb7a24f91d509ab93d130f64f582c831e998bd8e1 (patch)
tree77bfa7d54557cf0aef45e0f0133cb354065eafec
parentfc431270ac75235a1b5bfa6f5cac780e49199e68 (diff)
downloadcpython-b7a24f91d509ab93d130f64f582c831e998bd8e1.zip
cpython-b7a24f91d509ab93d130f64f582c831e998bd8e1.tar.gz
cpython-b7a24f91d509ab93d130f64f582c831e998bd8e1.tar.bz2
Blocked revisions 76782 via svnmerge
................ r76782 | lars.gustaebel | 2009-12-13 12:42:29 +0100 (Sun, 13 Dec 2009) | 28 lines Merged revisions 76780 via svnmerge from svn+ssh://pythondev@svn.python.org/python/trunk ........ r76780 | lars.gustaebel | 2009-12-13 12:32:27 +0100 (Sun, 13 Dec 2009) | 21 lines Issue #7357: No longer suppress fatal extraction errors by default. TarFile's errorlevel argument controls how errors are handled that occur during extraction. There are three possible levels 0, 1 and 2. If errorlevel is set to 1 or 2 fatal errors (e.g. a full filesystem) are raised as exceptions. If it is set to 0, which is the default value, extraction errors are suppressed, and error messages are written to the debug log instead. But, if the debug log is not activated, which is the default as well, all these errors go unnoticed. The original intention was to imitate GNU tar which tries to extract as many members as possible instead of stopping on the first error. It turns out that this is no good default behaviour for a tar library. This patch simply changes the default value for the errorlevel argument from 0 to 1, so that fatal extraction errors are raised as EnvironmentError exceptions. ........ ................
0 files changed, 0 insertions, 0 deletions