I would like to see a patch that does this: 1) add a new attribute "variables?" to the RestictedError object and make sure they are saved, loaded. 2) When a ResrictedError is raised identify all relevant variables and save them in the new attribute. 3) modify the admin/ticket view to display those variables.
I think this should be possible by just editing the gluon/ restricted.py module. Massimo On Sep 13, 6:00 pm, Thadeus Burgess <[email protected]> wrote: > The goal of web2py if im not mistaken, is to provide an all-in-one > environment for students to develop python web applications while adhearing > to security and standards. So that there is no need for external > debuggers/ide. If not, then what is the point of even including a file > editor with web2py? > > I would think that would be reason enough to add a varaible trace. > > When your dealing with external data that you cannot control, I don't see > how you could get away without having variable traces. > > Especially if you are dealing with random data, that might throw an > exception every once in a while > > Sure, i could write a debugger that will write to a file to print the > variables in question... > > Or use one of the many python ide's where the debuggers work maybe a quater > of the time (if that), and they don't even know whats going on inside of > web2py. > > - Thadeus > > On Sun, Sep 13, 2009 at 5:38 PM, Yarko Tymciurak <[email protected]> wrote: > > ve never been compelled for this (in compiled code, perhap --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
