#23341: Better stacktrace error for makemigrations when migration references
nonexistent migration(s)
--------------------------------------+------------------------------------
Reporter: rsalmaso | Owner: nobody
Type: Cleanup/optimization | Status: closed
Component: Migrations | Version: 1.7-rc-3
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"abd640fbdfce2c8dc8bca039525694d3a1a0297a"]:
{{{
#!CommitTicketReference repository=""
revision="abd640fbdfce2c8dc8bca039525694d3a1a0297a"
Fixed #23341 -- Added migration name to nonexistent migration error in
makemigrations.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23341#comment:5>
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/066.83b93de7e693a47ca2f2637ccaab2ea7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
