Changes between Initial Version and Version 12 of Ticket #23366


Ignore:
Timestamp:
12/30/14 13:01:37 (9 years ago)
Author:
Markus Holtermann
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #23366

    • Property Status changed from new to assigned
    • Property Cc Iacopo Spalletti added
    • Property Component changed from Uncategorized to Migrations
    • Property Needs tests set
    • Property Version changed from 1.6 to 1.7
    • Property Easy pickings set
    • Property Owner changed from nobody to Iacopo Spalletti
    • Property Has patch set
    • Property Type changed from Uncategorized to Bug
    • Property Triage Stage changed from Unreviewed to Accepted

  • Ticket #23366 – Description

    initial v12  
    55I 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:
    66
    7 There's still a subtle gotcha where `makemigrations --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.
     7There'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.
    88
    99It's a corner case, sure, but likely will lead to user frustration for those stuck in that corner.
Back to Top