> > How can we step through the TurboGears Python code? > you could start with http://docs.python.org/lib/module-pdb.html Hmm, I am looking for a UI-based debugger, but probably there is a way to pu WinPdb over the module-pdb. Just one quick newbie question: did anybody see this module-pdb working with exactly TurboGears? :)
> another approach will be to use the logger which is a new feature since ( > 0.9a6?) anyway I wrote a tutorial oriented to someone that has never use the > logger before http://trac.turbogears.org/turbogears/wiki/logging and I jsut > found out I forgot to link it from the main wiki page thanks for that :) Hmm, I am using the preview version and its dev.cfg includes the "logging" section. I wonder where the default debug_out handler logs to? > > If TurboGears wants to reach the big audience (and it definitely > > wants) the debugging methods for Windows are a must. > Why windows? you need that for all OS. Because Windows is a mass market :) It is just great to have a solution for several platforms. And that's why I try to use the cross-platform (and also cross-language) Eclipse whenever possible. > my personal approach when something goes really wrong is that I try to > reproduce it on a python console Good way, but anyway at the moment I am interested in using debugger for learning TurboGears, not that much for debugging ;) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears -~----------~----~----~----~------~----~------~--~---
