One GOTCHA I found with WING IDE is that you must delete all .pyc files before running, in order to have it correctly stop on your breakpoints in non-module code, in the case where such .py source has been subsequently modified after the .pyc was created. For code that is in a module, the breakpoints always stop correctly regardless of changes to the .py of the module.
On Thursday, April 23, 2009 12:51:21 AM UTC-5, Speedbird wrote: > > Folks, > > Just wanted to share with the community a real jewel, many of you knew > this but I actually started using it "heavily" during the past couple > of weeks: the IDE is wing from wingware, basically you run web2py from > inside of it, then just open your controller/module/model from the > IDE, set up a breakpoint and voila you have a very interesting > development "studio" ala visual studio. > > I've added a screenshot of my desktop running the IDE with my current > pet, pyforum.org being "debugged", the screenshot can be found here: > http://www.julioflores.com/static/debug_web2py.png > > Wing IDE is not free, BUT you can get a developer's license (which > will give you the latest "Pro" release bona-fide). you have no idea > how much less time I've spent debugging the code with a tool like this > one, long live web2py > > PS - Here's the web2py-specific information on their page, whoever > wrote it must've had a good understanding of the web2py framework (was > it you massimo??) - http://www.wingware.com/doc/howtos/web2py > > Best regards to all, > > Julio > > --
