On Jul 5, 7:33 pm, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > Having an exception > for every possible response code is really overkill here, since it means > you'll be raising status-code-related exceptions instead of more > semantic ones.
Ah, makes sense. > > * Shouldn't Django be consistent in its own raising of errors and > > choose one way to do it (e.g. choose #1 above over #2)? Out of > > curiosity I grep'd the code to count how many chose the paren method > > vs the comma method: > > Meh. They're both perfectly valid Python and people should be able to > read either. It really makes no significant difference at all. I tend to > use the parenthesised version in my own code (partly because it's easier > to split across multiple lines), but the other form is just as readable. Agreed. Not worth it. Thanks for the reply Malcolm. Very informative as always. -Rob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
