Pythoscope dies if a point of entry throws a string exception
Bug #522364 reported by
Pieter Van Dyck
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Pythoscope |
Fix Released
|
Medium
|
Michal Kwiatkowski | ||
Bug Description
To reproduce:
generate a point of entry with "raise 'exception message'"
Revision history for this message
| Michal Kwiatkowski (ruby) wrote | #1 |
| Changed in pythoscope: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| assignee: | nobody → Michal Kwiatkowski (ruby) |
| importance: | Medium → Undecided |
| milestone: | none → 0.4.3 |
| importance: | Undecided → Medium |
Revision history for this message
| Michal Kwiatkowski (ruby) wrote | #2 |
| Changed in pythoscope: | |
| status: | Confirmed → Fix Committed |
| Changed in pythoscope: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
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(
Pythoscope doesn't fail and continues inspection in this case.