Re: [Django] #21280: Avoid generating empty migrations on serialization failures

2013-10-17 Thread Django 
#21280: Avoid generating empty migrations on serialization failures
-+-
 Reporter:  timo |Owner:  Tim
 Type:  Bug  |  Graham 
Component:  Migrations   |   Status:  closed
 Severity:  Normal   |  Version:  master
 Keywords:   |   Resolution:  fixed
Has patch:  0| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"50087063450b3134461f2c4c5a36c3dd8ec1980c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="50087063450b3134461f2c4c5a36c3dd8ec1980c"
 Added test for a921f06 - refs #21280.

 This commit also lays the groundwork for future tests for the
 makemigrations command.
 }}}

-- 
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/062.e3ec7143462d1bc494e301bc5d51fe01%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21280: Avoid generating empty migrations on serialization failures

2013-10-17 Thread Django 
#21280: Avoid generating empty migrations on serialization failures
-+-
 Reporter:  timo |Owner:  Tim
 Type:  Bug  |  Graham 
Component:  Migrations   |   Status:  closed
 Severity:  Normal   |  Version:  master
 Keywords:   |   Resolution:  fixed
Has patch:  0| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Tim Graham ):

 * owner:   => Tim Graham 
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"a921f0634583e2f87475e802e2674e7159b4f25b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a921f0634583e2f87475e802e2674e7159b4f25b"
 Fixed #21280 -- Don't generate empty migration files
 }}}

-- 
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/062.cb42bec9f0cd435f5cfef4008ffe13fa%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21280: Avoid generating empty migrations on serialization failures

2013-10-17 Thread Django 
#21280: Avoid generating empty migrations on serialization failures
+
 Reporter:  timo|Owner:
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by tuxcanfly):

 Submitted a simple fix: https://github.com/django/django/pull/1761

-- 
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/062.d0dc9e84a21afac3adac43b55cdfa605%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #21280: Avoid generating empty migrations on serialization failures

2013-10-16 Thread Django 
#21280: Avoid generating empty migrations on serialization failures
--+
   Reporter:  timo|  Owner:
   Type:  Bug | Status:  new
  Component:  Migrations  |Version:  master
   Severity:  Normal  |   Keywords:
   Triage Stage:  Accepted|  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+
 If a model fails to serialize, an empty migration file will be generated
 which needs to be removed manually. You'll get an error like
 "django.db.migrations.loader.BadMigrationError: Migration 0001_initial in
 app auth has no Migration class" if you try to migrate without doing so.

 We should either verify that there won't be any errors before creating the
 migration file or remove the empty file if there is an error.

-- 
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/047.194b2cc865aa0ba72690351213082200%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.