Hide Forgot
abrt version: 1.1.18 architecture: x86_64 cmdline: /usr/bin/python /usr/bin/pep8 com component: python-pep8 executable: /usr/bin/pep8 kernel: 2.6.35.13-91.fc14.x86_64 package: python-pep8-0.6.0-2.fc14 reason: pep8.py:723:readlines:IOError: [Errno 2] No such file or directory: 'com' release: Fedora release 14 (Laughlin) time: 1306162496 uid: 500 backtrace ----- pep8.py:723:readlines:IOError: [Errno 2] No such file or directory: 'com' Traceback (most recent call last): File "/usr/bin/pep8", line 9, in <module> load_entry_point('pep8==0.6.0', 'console_scripts', 'pep8')() File "/usr/lib/python2.7/site-packages/pep8.py", line 1346, in _main runner(path) File "/usr/lib/python2.7/site-packages/pep8.py", line 1027, in input_file errors = Checker(filename).check_all() File "/usr/lib/python2.7/site-packages/pep8.py", line 827, in __init__ self.lines = readlines(filename) File "/usr/lib/python2.7/site-packages/pep8.py", line 723, in readlines return open(filename).readlines() IOError: [Errno 2] No such file or directory: 'com' Local variables in innermost frame: filename: 'com' comment ----- I tried to run pep8 on a "compare.py" but the tab completion blocked and I ran pep8 only on "com". Pep8 should catch the exception if the file against which one try to run it doesn't exist. For example: $ pep8 blasdlkjalfhvhdnvuhbad How to reproduce ----- 1. run pep8 with an invalid argument 2. 3.
Created attachment 500452 [details] File: backtrace
Hey Ian, may I ask why this resolution ?
Because I don't think it's a bug :) The exception very plainly says what's going on, it's meant to be a command line application used by Python developers that understand exceptions, and the only reason it's here is because abrt caught it because it's an exception. If you believe catching the exception is trivial, please send a patch upstream.