Timing issue with testing and custom Querysets

[adam@…]

If you run two identical tests while using a custom queryset method, all test access to the same queryset seems fail (same or different views). The view returns and empty queryset.

This repo is a full project just to reproduce the bug and has notes on how to get it to pass in different ways. If I am an idiot, I'm sorry. This manifested in a large project and I stripped it down to what it is now which is the bare minimum.

​https://github.com/adamrt/django-queryset-issues

Django 1.6.5 and 1.7c1
Python 2.7.3 and 2.7.5
MaxOS X 10.9 and Ubuntu 12.04
PostgreSQL and SQLite3

[Tim Graham]

I couldn't run your project out of the box (AppRegistryNotReady exception), but I had no problems after the following modification:

diff --git a/myapp/models.py b/myapp/models.py
index 6130f0c..4fe32cb 100644
--- a/myapp/models.py
+++ b/myapp/models.py
@@ -14,4 +14,5 @@ class Entry(models.Model):
 
 
 class EntryListView(ListView):
-    queryset = Entry.objects.published()
+    def get_queryset(self):
+        return Entry.objects.published()

Could you test it?

[adam@…]

I apologize for the AppRegistryNotReady error. I was between 1.7c1 and 1.6.5 with the manager/queryset situation and requirements.txt. I have no problem just overriding get queryset. Just seemed like unusual behavior to me but it's not a big deal to me.

Just trying to do my part. The app seemed so minimal that it seemed like other people had to be hitting the same issue but I couldn't find it anywhere.

Feel free to close this ticket if you are satisfied, as I will just override get_queryset.

Thanks!

[Tim Graham]

The issue is that passing callable arguments to querysets doesn't really work as you might expect. We've actually deprecated doing so in 1.7 (see f1b3ab9c2158f5a7da113aef4158499ce2d42ee2). I think that'll clear up the confusion.