On Tue, 2009-02-17 at 19:25 -0600, Jeremy Dunck wrote: > On Tue, Feb 17, 2009 at 7:13 PM, Malcolm Tredinnick > <[email protected]> wrote: > ... > >> if settings.DEBUG and self.prior_iteration: > >> warnings.warn("dope!") > > > > This certainly sounds reasonable and doable today without any real > > overhead. Go ahead and make a patch/ticket. > > OK. > > Do you think there should be a PerformanceWarning class, or just use > the default UserWarning?
It should be blue! :-) Slight preference for using a standard warning type at the moment. Either UserWarning or RuntimeWarning. Only a slight preference, though. Please yourself here. Please don't ask me what to do about issuing multiple times, because I was thinking about that over lunch just now and it may be fiddly. Issuing a warning always sounds right, since it's commonly going to be a property of a template that will cause this to happen. But if you use that template and hit a problem, you're going to be swamped with warnings. We really need a "once per template" option that obviously doesn't exist in the warnings module. I might be over-thinking it, though. "Always" is probably the right answer. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
