Tim Chase wrote: >>> Any other tips to getting up to speed fast? >>> >> With the internal code? I wish there was some silver bullet like that. >> > > I found James Bennett's page[1] on "How Django processes a > request" helpful for understanding the big picture of how the > pieces fit together. It helps makes sense of flow as you wade > through the Python source. > > Additionally, learning the basics of "pdb"[2] (python's > batteries-included debugger) can help as your view can just include > > include pdb; pdb.set_trace() > > before the line you want to investigate (or even at the top of > your view), and the dev-server will pause at that point, allowing > you to debug from there. > > -tim > > > [1] > http://www.b-list.org/weblog/2006/jun/13/how-django-processes-request/ > > [2] > http://www.google.com/search?q=python%20pdb%20tutorial > > > > > > > I found the best resource was djangobook.com
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
