#22251: Dumpdata improvement suggestions
-------------------------------------+-------------------------------------
Reporter: Gwildor | Owner: nobody
Type: | Status: closed
Cleanup/optimization | Version: master
Component: Core (Management | Resolution: invalid
commands) | Triage Stage:
Severity: Normal | Unreviewed
Keywords: | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by Gwildor):
I must say I was already anticipating that, so I wasn't surprised by your
reaction, but I decided in the end that one big coherent story would be
better to illustrate the point. But maybe the Django-developers group was
a better place to do that. Anyway, thanks for taking the time of reading
it!
I've opened seperate tickets for the suggestions: #22257, #22258 and
#22258.
--
Ticket URL: <https://code.djangoproject.com/ticket/22251#comment:2>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.af1e3c85c39321e0f9047f9979b6eb77%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
