Description

Check that the abrt handles Python exceptions.

How to test

First, confirm in /etc/abrt/plugins/Python.conf that the Python addon is enabled. The conf file should contain this line:
```
Enabled = Yes
```
Next, ensure that /etc/abrt/abrt.conf has at least one reporter defined for the Python addon. For example,
```
Python = Logger, Mailx
```
Restart service
```
service abrtd restart
```
Find a python .py file in system originally installed via RPM. For this test, we will choose /usr/share/doc/smolt-1.?/lite2my.py which is provided by the smolt package. First, save a back-up of the file:
```
cp /usr/share/doc/smolt-1.?/lite2my.py /tmp/
```
Now, edit the file /usr/share/doc/smolt-1.?/lite2my.py to contain some invalid Python code. For example,
```
#!/usr/bin/python
```
"11" + 11
Next, execute the modified file using python. For example, in terminal type:
```
python /usr/share/doc/smolt-1.?/lite2my.py
```

Revert the modified python file

cp /tmp/lite2my.py /usr/share/doc/smolt-1.?/lite2my.py

Python traceback should be generated
ABRT catches it, check the report via abrt-gui whether the trace in report window is the same as in terminal
The python is run with every python script, so any bug in the hook may have bad consequences for all python app. So please pay attention to any weird behaviour of python scripts after abrt's pyhook is installed.