On Fri, Oct 29, 2010 at 2:50 PM, Ivan Sagalaev <man...@softwaremaniacs.org> wrote: > Russel: >>> >>> Wouldn't it make sense to put a flag on the TemplateResponse >>> that prohibits accidental baking? > > Mikhail: >> >> So maybe it will be better not to make bake/force_bake public so that >> users won't be able to shoot themselves in the foot? > > I don't think it's doable at all. People still can call any method in as > well as they can ignore or alter any protection flag. I believe it's > sufficient to abide to the Python way here, write a proper documentation and > treat people as grown-ups trusting them not to do bad things in their > process_template_response.
I agree that it's important to treat people as grown ups. However, this is something that is trivial to do by accident -- for example, printing response.content would be an obvious debug step -- and it will be a non-trivial thing to identify that this is the cause of your problems. Maybe an unconditional exception is a little strong, but some sort of safety catch seems called for. 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-develop...@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.
