#30467: `makemigrations app_label` sometimes tries to create migrations for
unrequested app_label
-------------------------------------+-------------------------------------
Reporter: Vsevolod Novikov | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Migrations | Version: 2.2
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* status: new => closed
* resolution: => invalid
Comment:
The _Workflow_ above already says "...then a new **set** of migrations
will be written out". That set is expected to include all the required
dependencies, as per the section I linked.
Your suggestion for expected behaviour was this:
> The makemigrations command with applied app_label should create a
migration for only noted app_label...
But that's just not the correct behaviour. Hence closing as invalid.
Please see TicketClosingReasons/DontReopenTickets.
--
Ticket URL: <https://code.djangoproject.com/ticket/30467#comment:3>
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/064.299b751d15e91a34577746a15efee200%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
