Peter's Blog

You have to worry when you have been using a tool for only a couple of days and you find bugs in the latest version.

If you single step through the following in komodo:

import BeautifulSoup

s = """\xe2"""

bs = BeautifulSoup.BeautifulSoup( s)

print bs

then when you get to the print statement the debugger gives up the ghost. It's stops showing local variables and it won't single step any further.

The problem appears to be something to do with the way BeautifulSoup overrides the __str__ function which the debugger is calling to display the value of bs. The strange character code generated by drupal date formatting triggers the problems.

wingide and the python debugger have no problems with this.

If I replace the odd character code with the correct html entity (as drupal should have in the first place) the komodo is happy:

import BeautifulSoup

s = """\xe2"""

bs = BeautifulSoup.BeautifulSoup( s.replace('\xe2', 'â'))

print bs

I think my final conclusion is that Komodo's debugger badly needs debugging itself. I'm not sure it is stable to a degree where I would want to spend good money on it. The whole point to me is to get a decent debugger, if I want to compromise I can stick with pdb.

Update: wingide finds an exception within BeautifulSoup which somewhere gets ignored and life goes on. Wingide seems generally better in when you single step, the step finishes and you are on the next line. Komodo has a tendency to go and not come back.