This bug manifests differently depending on which Python version is used to run pythoscope.
On Python 2.3 and 2.4 pythoscope fails silently after emitting "INFO: Inspecting point of entry" message.
Under Python 2.5 it fails with a traceback:
INFO: Inspecting point of entry o.py.
<string>:1: DeprecationWarning: raising a string exception is deprecated
Traceback (most recent call last):
...
File "<string>", line 1, in <module>
exception message
Under Python 2.6 string exceptions are no longer supported, which causes the following warning:
WARNING: Point of entry exited with error: TypeError('exceptions must be classes or instances, not str',)
Pythoscope doesn't fail and continues inspection in this case.
This bug manifests differently depending on which Python version is used to run pythoscope.
On Python 2.3 and 2.4 pythoscope fails silently after emitting "INFO: Inspecting point of entry" message.
Under Python 2.5 it fails with a traceback:
INFO: Inspecting point of entry o.py.
<string>:1: DeprecationWarning: raising a string exception is deprecated
Traceback (most recent call last):
...
File "<string>", line 1, in <module>
exception message
Under Python 2.6 string exceptions are no longer supported, which causes the following warning:
WARNING: Point of entry exited with error: TypeError( 'exceptions must be classes or instances, not str',)
Pythoscope doesn't fail and continues inspection in this case.