Changes between Initial Version and Version 12 of Ticket #23366
- Timestamp:
- Dec 30, 2014, 7:01:37 AM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #23366
- Property Component Uncategorized → Migrations
- Property Easy pickings set
- Property Type Uncategorized → Bug
- Property Version 1.6 → 1.7
- Property Triage Stage Unreviewed → Accepted
- Property Owner changed from to
- Property Status new → assigned
- Property Has patch set
- Property Needs tests set
- Property Cc added
-
Ticket #23366 – Description
initial v12 5 5 I just hit what appeared to be the same issue myself, found the ticket, checked my Django version (1.7 RC3) and thought all should be well, but I thought it still wasn't working for me until I actually read the patch and saw why: 6 6 7 There's still a subtle gotcha where `m akemigrations--list` will still throw the dependency error, while `makemigrations <app name>` will happily run. So if someone gets Dependency on app with no migrations when starting `runserver` and they then try to check their migrations list, they will be prevented from doing so and they have no cue to as to what they can do to remedy things.7 There's still a subtle gotcha where `migrate --list` will still throw the dependency error, while `makemigrations <app name>` will happily run. So if someone gets Dependency on app with no migrations when starting `runserver` and they then try to check their migrations list, they will be prevented from doing so and they have no cue to as to what they can do to remedy things. 8 8 9 9 It's a corner case, sure, but likely will lead to user frustration for those stuck in that corner.