#27350: Attaching signals to abstract models don't work as it used to be
     Reporter:  Florent Messa        |                    Owner:  nobody
         Type:  Bug                  |                   Status:  new
    Component:  Database layer       |                  Version:  1.10
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:
     Keywords:                       |             Triage Stage:
                                     |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0

Comment (by Florent Messa):

 Replying to [comment:1 Tim Graham]:
 > Hi, you should
 tickets/#bisecting-a-regression bisect] to find the commit where the
 behavior changed. If I had to guess it might be
 ed0ff913c648b16c4471fc9a9441d1ee48cb5420 or

 It was introduced by 3a47d42fa33012b2156bf04058d933df6b3082d2

 Build is available on [[https://travis-ci.org/thoas/django-signals-
 wtf/builds/167683086|travis]], **110a** is the parent commit of
 3a47d42fa33012b2156bf04058d933df6b3082d2 and **110b** is located at

Ticket URL: <https://code.djangoproject.com/ticket/27350#comment:2>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
For more options, visit https://groups.google.com/d/optout.

Reply via email to