On Sun, May 8, 2011 at 10:13 PM, Adam Seering <aseer...@mit.edu> wrote:
> (Incidentally, sorry if this is a duplicate; my original reply, > identical text, doesn't show up on groups.google.com...) > I don't know why, but google groups decided your original message might be spam so held it. When it makes that decision for anyone other than a new user, it doesn't bother to send a note to moderators until a few days later. It's a great feechur of google groups. I have removed the copy that was held for moderation so as to avoid the duplication. The change you have noticed is documented in the 1.3 backwards-incompatibility list: http://docs.djangoproject.com/en/1.3/releases/1.3/#use-of-custom-sql-to-load-initial-data-in-tests Of the alternatives you list, using setUp seems like the correct approach. I'm a little confused by your worry both that you're inevitably going to forget to put a call somewhere where it is needed and simultaneous statement that it's going to be causing duplicate work in a lot of places where it isn't really needed, though. It seems like you ought to be able to figure out where it is needed and put it there (possibly helped by tests that fail due to it not being there). Karen -- http://tracey.org/kmt/ -- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
