Re: [Django] #29755: Infinite migrations created after removing Meta.default_related_name

[Django]

#29755: Infinite migrations created after removing Meta.default_related_name
-+-
 Reporter:  Aamir Rind   |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.11
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
  migrations,unlimited,infinite,makemigrations|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"a4495f4b989dc919d80fcf9f38e31e247faa94fb" a4495f4b]:
 {{{
 #!CommitTicketReference repository=""
 revision="a4495f4b989dc919d80fcf9f38e31e247faa94fb"
 Fixed #29755 -- Made migrations detect changes to
 Meta.default_related_name.
 }}}

-- 
Ticket URL: 
Django 
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 
https://groups.google.com/d/msgid/django-updates/070.101482365ba3e61966abb43ed7fe6a93%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29755: Infinite migrations created after removing Meta.default_related_name

[Django]

#29755: Infinite migrations created after removing Meta.default_related_name
-+-
 Reporter:  Aamir Rind   |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.11
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
  migrations,unlimited,infinite,makemigrations|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"4c5a8c6f50577daa8b8aaef28a8f32ab34185e80" 4c5a8c6]:
 {{{
 #!CommitTicketReference repository=""
 revision="4c5a8c6f50577daa8b8aaef28a8f32ab34185e80"
 [2.1.x] Fixed #29755 -- Made migrations detect changes to
 Meta.default_related_name.

 Backport of a4495f4b989dc919d80fcf9f38e31e247faa94fb from master
 }}}

-- 
Ticket URL: 
Django 
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 
https://groups.google.com/d/msgid/django-updates/070.fe309ddd3b6a5e3b6298852cfc963d38%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29755: Infinite migrations created after removing Meta.default_related_name

[Django]

#29755: Infinite migrations created after removing Meta.default_related_name
-+-
 Reporter:  Aamir Rind   |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
  migrations,unlimited,infinite,makemigrations|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * stage:  Accepted => Ready for checkin


Comment:

 Yep. Looks good.

-- 
Ticket URL: 
Django 
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 
https://groups.google.com/d/msgid/django-updates/070.c30a25c1ab64c7ea67c6958c3ea63dbb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29755: Infinite migrations created after removing Meta.default_related_name

[Django]

#29755: Infinite migrations created after removing Meta.default_related_name
-+-
 Reporter:  Aamir Rind   |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  migrations,unlimited,infinite,makemigrations|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

 * owner:  nobody => Simon Charette
 * status:  new => assigned
 * has_patch:  0 => 1


Comment:

 It was a simple matter of adding the option to
 `AlterModelOptions.ALTER_OPTION_KEYS`

 https://github.com/django/django/pull/10389

-- 
Ticket URL: 
Django 
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 
https://groups.google.com/d/msgid/django-updates/070.9c8a60089039d995c932b8ead981d915%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29755: Infinite migrations created after removing Meta.default_related_name (was: Infinite Django Migrations)

[Django]

#29755: Infinite migrations created after removing Meta.default_related_name
-+-
 Reporter:  Aamir Rind   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  migrations,unlimited,infinite,makemigrations|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * component:  Core (Management commands) => Migrations
 * version:  2.1 => 1.11
 * stage:  Unreviewed => Accepted


Comment:

 Bug report seems to be against Django 1.11 but I verified that it affects
 master as of today (1b1f64ee5a78cc217fead52cbae23114502cf564).

-- 
Ticket URL: 
Django 
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 
https://groups.google.com/d/msgid/django-updates/070.aa0767b811278fec961f76fe1e838821%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.