#32247: "App does not have migrations" message could be more helpful
-------------------------------------+-------------------------------------
Reporter: berzi | Owner: (none)
Type: | Status: new
Uncategorized |
Component: Error | Version: 3.1
reporting | Keywords: documentation,
Severity: Normal | errors, error messages
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 1
UI/UX: 1 |
-------------------------------------+-------------------------------------
It has happened to me and probably many many others several times that
running
{{{
manage.py migrate SOME_APP
}}}
would yield an error like
{{{
CommandError: App 'SOME_APP' does not have migrations.
}}}
all while a migrations folder with migrations *does exist* in the
specified app. It is often the case that the cause of the issue is simply
that the `__init__.py` file is missing from the directory, but that is not
at all apparent. Even running
{{{
manage.py showmigrations SOME_APP
}}}
is unhelpful and unless the programmer is specifically aware of this
potential issue (and even then it's easy to forget) the problem can be
confusing to solve.
I propose a simple change of the error message to:
{{{
CommandError: No migration detected for app 'SOME_APP'. Is an
'__init__.py' file present in the 'migrations/' directory?
}}}
Or something to the same effect.
--
Ticket URL: <https://code.djangoproject.com/ticket/32247>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/048.630acde9e6a056036fe068fd69fe6d68%40djangoproject.com.
