summaryrefslogtreecommitdiff
path: root/Python/getcompiler.c
diff options
context:
space:
mode:
authorLars Gustäbel <lars@gustaebel.de>2009-12-13 11:32:27 +0000
committerLars Gustäbel <lars@gustaebel.de>2009-12-13 11:32:27 +0000
commit92ca7561bb52fbe934e5d5372bc34a4b904edf6a (patch)
tree823910abf2935a6cf61138643ecf32fd3d1f9796 /Python/getcompiler.c
parent5f429e02274f85f4ba19276847e323b13fae6568 (diff)
downloadcpython-git-92ca7561bb52fbe934e5d5372bc34a4b904edf6a.tar.gz
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.
Diffstat (limited to 'Python/getcompiler.c')
0 files changed, 0 insertions, 0 deletions