On Thu, Feb 10, 2011 at 12:46 PM, Sameer Rahmani <lxsam...@gmail.com> wrote: > Hi Russell > > that patch is just a lazy code as i said before, but the idea will > implements in better ways. it will be a good idea to use such code in > development web server as an option. so user can easily use it, but using > hooks and building and external tool is not a good way to deal with > debugging matter, (in my point of view), > > why? > > because internal debugging facilities is important parts of a framework, the > problem with external tools is that user have to do extra work to use them, > but using an option like "python manage.py runserver --debug" is not a big > deal.
That's fine, and I can agree with the sentiment -- but it's also not what you included in your patch. I can only comment effectively on code that I can actually see. I would also point out that a hardcoded solution allow for exactly one solution -- the solution you provide. However, if you provide a hook, the entire community can collaborate to build bigger and better tools that exploit that hook. That doesn't preclude shipping an out-of-the-box, easy-to-use tool that exploits the same hook. Yours, Russ Magee %-) -- 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.
