Description of problem: pep8 non-python-file Version-Release number of selected component: python-pep8-1.0.1-1.fc17 Additional info: libreport version: 2.0.16 abrt_version: 2.0.16 cmdline: /usr/bin/python /usr/bin/pep8 localization-test-report-1.txt kernel: 3.6.2-4.fc17.x86_64 backtrace: :unindent does not match any outer indentation level (<tokenize>, line 25) : :Traceback (most recent call last): : File "/usr/bin/pep8", line 9, in <module> : load_entry_point('pep8==1.0.1', 'console_scripts', 'pep8')() : File "/usr/lib/python2.7/site-packages/pep8.py", line 1348, in _main : runner(path) : File "/usr/lib/python2.7/site-packages/pep8.py", line 1023, in input_file : errors = Checker(filename).check_all() : File "/usr/lib/python2.7/site-packages/pep8.py", line 949, in check_all : for token in tokenize.generate_tokens(self.readline_check_physical): : File "/usr/lib64/python2.7/tokenize.py", line 351, in generate_tokens : ("<tokenize>", lnum, pos, line)) : File "<tokenize>", line 25 : 10: cs.UTF-8 cs_CZ.UTF-8 0 1 'Czech' : ^ :IndentationError: unindent does not match any outer indentation level
Created attachment 634975 [details] File: dso_list
Created attachment 634976 [details] File: smolt_data
Created attachment 634977 [details] File: core_backtrace
This crash report appears to be for running pep8 on obviously incorrect code, and a traceback is to be expected. Reporter, you may reopen this ticket -- with more information on why this is a bug -- if you believe the above is incorrect.
That makes about as much sense as saying that a C compiler that core dumps on invalid code is working as expected. The proper thing to do here is to display an informative error message, not a traceback.
This isn't a compiler, it's a code cleanup tool. If your code cleanup tool can't read your code, there is either a major bug in the tool or your code has major problems. In this case I see the latter. If you really think it shouldn't throw an exception, please file an issue upstream: https://github.com/jcrocholl/pep8