Hi, i was working in a project with a very complex logic, and i mixed up with logical problems in the code. i used some debugging methods and tools like ipdb, pdb.set_trace(), django-command-extension and etc. but at last i end up with a little django patch #15249.
that patch provide a easy way to debug django code at the exception raise time. i discussed about the inline debugging idea in irc developer channel with some cool guys :D, and i decided to post this mail to share the idea with others and get their ideas. what does #15249 patch do? it run a pdb or ipython shell when an exception raised with the namespaces of raised trackback, (if settigns.INLINE_DEBUGGER set to correct value), so it will be very easy to test some code. why don't you use: * pdb.set_trace()? because i have to write some code in each module that i want to debug and also i can't test some code snippet in the runtime env (as far as i know) * ipdb? same as pdb and its and external module and i cant expect my friend to install that too. * django-command-extension? it's an external tool too, its very cool but don't have some of ipython feature like code completer. #15249 patch is a little and lazy code, but it will be a good idea for django to provide such functionality. what's your idea about it ? i know, i talk to much :P -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
