On Sun, Sep 22, 2013 at 5:09 PM, Shai Berger <[email protected]> wrote:
> If this is agreed, then we should add an assertNoQueries, deprecate the > existing assertNumQueries, and add a new assertNumQueries that takes a > backend > specification, shouldn't we? This is regardless of what we do with @atomic. assertNumQueries is fine as is, it's just been used poorly. I think passing something to identify the backend would lead to a more awkward usage and tests that assert nothing depending on the backend. It's better to have the test fail in those situations instead of assert nothing. -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
