Peter's Blog

Redefining the Impossible

WingIDE Update


I'm still on the WingIDE trial and I am still using it. It is a big help using a debugger instead of print statements. Thoughts/observations:

  • it still runs like treacle.
  • when I edit a file in VIM and write it to disk, WingIDE immediately asks if I want to reload it. Other IDEs I use take the less annoying approach of waiting until I switch back to the IDE.
  • still not crashed or shown any severe bugginess.
  • in a language like python I find it strange that WingIDE does not allow me to 'edit and continue' as Visual C++ and Visual Basic 6 have been doing for about 8 years. Whenever I edit anything I have to stop and restart. If it can reload modules then I haven't found out how. To make this even more irritating, Wing always stops on the first line of the first file when the program restarts so I have to press the go button. Given the slowness Wing, I end up waiting for this halt so I am ready to press the button and get going again.
  • I had a quick look a Komodo but, as I suspected, I would have to use the ActiveState python distribution. I stopped using that years ago as it's release cycle lagged behind 'real' python's and 'real' python was 100% satisfying. ActiveState spent years dicking around trying to make perl work with COM, making it difficult to embed in anything else in the process. I'm not a total fan of ActiveState.

Filed under: python vim wingide

3 Comments

ScanmasterG Says:

over 4 years ago

Peter,

Your comment regarding Komodo is erroneous. You do not have to use ActiveState's Python distro at all. I have quite happily used it with Python 2.3/2.4 from the python.org website. It also has a fully featured visual debugger.

Grant

Peter Says:

over 4 years ago

Thank you for the correction, I'll give it another try.

Apart from the python debugging it does have a nice regular expression editor that I'd like to have to hand.

Peter

Ludvig Ericson Says:

over 3 years ago

Oh but that Python debugger can make Komodo stall indefinately, and just like WingIDE you have to restart the debugging session if it breaks the code, otherwise the process won't continue at all - and breakpoints won't work as far as I'm seeing.

Sorry but comments on this post are now closed.