Well it could be put into web2py.py or the model or the controller. However, this has to be maintained when upgrading to the next version of the svr. Thus it becomes a maintainance issue. Oh sure, this isn't the end of the world, but if it weren't for this password thing, I'd think that they could attach without the code snippet in the source. I've run Visual Studio for years, attaching to running processes and never had to bother with this - you'd think they'd provide a default password. Most of my colleagues would add then delete code snippets to attachthe debugger - but this is not necessary.
But here's the thing. The code snippet has to be RUN before you try to attach with Winpdb. Thus is you put it into your model then you must first request a webpage before you can attach the debugger. By putting it into web2py.py I can start the svr and then attach before any of my code gets run. That is I select 'attach' from Winpdb's main menu. Can Winpdb be automatically launched and attached from that code snippet? Hmm I was putting it into web2py so that the seb2py process would show up in the 'attach' list in Winpdb. Maybe I don't know enough about this. --- Rb On Jul 28, 3:02 pm, Fran <[email protected]> wrote: > On Jul 28, 10:52 pm, rb <[email protected]> wrote: > > > I'm not crazy about having to modify code in > > web2py.py in order to do debugging. I've never used a debugger before > > that forced me to modify code. > > Could you not just have it as a line in your model which you can > easily comment-out when going into production? > > F --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
