This is probably a little OT, but you may be able to step through Python code using IronPython (Python .NET) and Visual Studio... really not sure about this. I'm not sure how much of TurboGears would run under IronPython either. There is a neat intro to IronPython here:
http://msdn.microsoft.com/msdntv/episode.aspx?xml=episodes/en/20051110PythonJH/manifest.xml [EMAIL PROTECTED] wrote: > > well I believe WinPdb just calls the debugger below :) > > No I haven't seen it, never needed to > > stuff always just works, that why I love it. > > Well, Eclipse + PyDev's debugger also always works with just a Python > script, but doesn't with TurboGears (at least I can't make it work) > > > your configuration is divided in two parts, > > there is a <project>/<package>/config dir where all non-deployment specific > > configurations go. > > you should have a log.cfg there (since 0.9a5 I think) > Thank you. Now I see my log prints > > > > Because Windows is a mass market :) > > not for server apps > But for server apps developers. And also for learners and students. A > lot of people like trying the server stuff on the developer's machine > before deploying it into real server environment. And mass market > developer's machine is under Windows. It is not to say that *nux is > bad, no way! It is just to emphasize the need for the Windows based > quickstart. > > > don't debug trust the source > Stepping through the code is my way of learning the code. And AFAIK > some other people also like this way. Probably it's about the personal > preferences :) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
