after going back and forth a bit with WING support guys... it appears to be an issue with Web2py...
on line 388 of compileapp.py there are two lines of code that only run on GAE... which essentially cache the compiled? code file using filename + ':' + key... where key is the function name. this ccode object then gets executed with a path of (this is my test example): "C:\SVNs\T4H\Buttrcup\www\applications\init\controllers \default.py:test" Since this is an invalid path, if there are any breakpoints set in the controller, Wing cannot hit them because it doesn't know where this file is. If I comment out the GAE caching function, then Wing hits its breakpoints correctly. if this is not a bug, and there is some other configuration settings I should be doing in order to debug with Wing, would someone kindly inform me? Thank you much, -Nick Franceschina On Jul 2, 12:55 pm, NickFranceschina <[email protected]> wrote: > I've been using WingIDE pro for a while... love it... followed advice > to get it setup to work with Web2py and runs fine if I launch debugger > through web2py.py ... but if I launch it through dev_appserver.py then > the server runs and the app works and the breakpoints are hit for all > code except for the controller code because, apparently, it is called > via python "exec" method... > > this works fine through web2py's web server... but not through > dev_appserver ... for me anyways.... > > What am I doing wrong? > > Thank you! > -Nick Franceschina
