#20795: Weird queryset behaviour and count() method
-------------------------------------+-------------------------------------
     Reporter:  maa@…                |                    Owner:  nobody
         Type:  Bug                  |                   Status:  closed
    Component:  Database layer       |                  Version:  1.5
  (models, ORM)                      |               Resolution:  invalid
     Severity:  Release blocker      |             Triage Stage:
     Keywords:  count queryset       |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by akaariai):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 There seems to be two things going on:
   1) You have overriden the model's init in a way that is incompatible to
 what Django expects. You can't add user arg to it, you might be able to
 use user kwarg instead. Basically, the signature must be `*args,
 **kwargs`, or Django will not be able to load your models back from DB.
   2) There is a bug in Python (IIRC) that causes errors inside list(qs) to
 swallow the error and return empty list. This is fixed in 1.6.

 So, marking this as invalid.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/20795#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" 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].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/074.832a36f89bf4ace005b3018e929fd777%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to