I tend to think that all diagnostics should reveal as much as they can
about their situation. So I bumped get() like this:
def get(self, *args, **kwargs):
...
clone = self.filter(*args, **kwargs)
...
if not num:
raise self.model.DoesNotExist("%s matching query does not
exist in %s."
% (self.model._meta.object_name, repr((args,
kwargs))))
That improved "Mod matching query does not exist" into "Mod matching
query does not exist in ((), {'name': 'yoData'})".
(Parenthetically, I did it because I have a long production JSON
fixture that I'd like to cut down into a short test-only fixture. But,
per my other appropriations, fixtures take too long to load, they
don't support comments like #, and they don't reveal their error
messages very well.
(I will deal by searching every "name": "foo" and replacing it with
"name": "_foo", then running all the tests. Any fixture the tests use,
I will take the _ out, and then I will erase every fixture that still
has its _.
(But this leaves open the problem that at test time, the diagnostic
gives no clue what record it sought. Hence my bio patch.)
So, is this already in there somewhere? Maybe in a version > 1.0.4? Or
would anyone like to add a cleaner version of it to the HEAD? Or does
it totally suck in some way I can't realize?
--
Phlip
http://penbird.tumblr.com/
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
