On May 15, 2013, at 9:01 PM, Jacob Kaplan-Moss <ja...@jacobian.org> wrote:
> Hi folks -- > > Does anyone have some clever thoughts on how to solve #16650? > > https://code.djangoproject.com/ticket/16550#comment:7 is a good > summary of the problem: if you're using extensions, you need a way to > run some custom SQL in tests after the DB gets created by the test > harness but before syncdb runs. > > The current patch and suggested solution on the ticket won't work (see > the thread), but I think it's a legit need and I'd like to come up > with a good solution and possibly reopen the ticket. > > Jacob > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > pre_syncdb signal? syncdb is still called in tests right? ----------------- Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message signed with OpenPGP using GPGMail
