#29636: Failing admin.E108 system check in 2.1
----------------------------------+--------------------------------------
     Reporter:  Petr Boros        |                    Owner:  nobody
         Type:  Bug               |                   Status:  new
    Component:  contrib.admin     |                  Version:  2.1
     Severity:  Normal            |               Resolution:
     Keywords:  SystemCheckError  |             Triage Stage:  Unreviewed
    Has patch:  0                 |      Needs documentation:  0
  Needs tests:  0                 |  Patch needs improvement:  0
Easy pickings:  0                 |                    UI/UX:  0
----------------------------------+--------------------------------------

Comment (by Petr Boros):

 Replying to [comment:5 Tim Graham]:
 > I think the report is missing some detail to reproduce the issue
 (perhaps some implementation detail of `PositionField`). For your case, it
 looks like
 
[https://github.com/django/django/blob/89d4d412404d31ef34ae3170c0c056eff55b2a17/django/contrib/admin/checks.py#L658
 hasattr(Trigger, 'position')] is failing which isn't the case for normal
 model fields.

 You are right, `hasattr(Trigger, 'position') == False`. However, at the
 same time, `'position' in Trigger.__dict__.keys() == True`.

 Why is that?

 I am attaching the full source code of `PositionField` to this ticket for
 reference. ''Note that the original source code comes from `django-
 positions` package.''

-- 
Ticket URL: <https://code.djangoproject.com/ticket/29636#comment:6>
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/067.5d515dfe3a5f5b8c3a95324a3f5286a6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to