#25561: dumpdata command cannot understand a dotted app name though
INSTALLED_APPS
allows it.
---------------------------+--------------------------------------
Reporter: tyrdare | Owner: nobody
Type: Bug | Status: new
Component: Utilities | Version: 1.7
Severity: Normal | Resolution:
Keywords: dumpdata | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------+--------------------------------------
Comment (by tyrdare):
I was able to reproduce the issue in sample I ginned up, which mimics the
same db architecture and module/submodule layout as the system I
encountered the problem on. However, in the process of working with my
sample, I came to realize that the dumpdata command works with the
app_labels of the models and that using
{{{
manage.py dumpdata app_label.ModelClassName
}}}
(where the model is in the models.py of the submodule) works just fine and
that I was doing it wrong on the original system.
When I ran into difficulties I was trying to do a
{{{
manage.py dumpdata app_label.subapp_label
}}}
which dumpdata reasonably considered to be a class
and
{{{
manage.py dumpdata app_label.subapp_label.ModelClassName'
}}}
which it considered to be an app
Please close as not a bug.
--
Ticket URL: <https://code.djangoproject.com/ticket/25561#comment:4>
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/065.2578f52d06322e8d8d9c4ebc2926caf7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
