On 4/27/07, Nicola Larosa <[EMAIL PROTECTED]> wrote: > > Ben Godfrey wrote: > > It was very hard to trace this to the Session.get_decoded method and it > > felt like a bit of a slap to find all pickle.loads exceptions being > > dropped silently. Is this really the best thing to do? Surely it would > > be better to raise the exception so that the programmer can see it? > > There are currently 36 naked "except" clauses in the Django trunk. Most of > them do something sensible, given each situation; a few just silence the > errors, which is not good enough. > > A nice idiom is used in several places: > > try: > ... > except: > if settings.DEBUG: > raise > > Let's have more of those. :-)
Suggestions and patches are always welcome. Tell us where you want them, and if we agree, we'll put them them in. Keep in mind that you need to convince us that each change is a good idea. To this end, you would be well advised to include a test case (or in this case, a broken model/view) that demonstrates why each change is required. 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 [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 -~----------~----~----~----~------~----~------~--~---
