Re: [Django] #5253: serializer for csv format for loaddata and dumpdata

6 views

Skip to first unread message

Django

unread,

Jan 26, 2015, 11:45:49 AM1/26/15

to django-...@googlegroups.com

#5253: serializer for csv format for loaddata and dumpdata
-------------------------------------+-------------------------------------
Reporter: Adam Schmideg | Owner: erob
<adam@…> |
Type: New feature | Status: new
Component: Core | Version: master
(Serialization) |
Severity: Normal | Resolution:
Keywords: csv, foreign keys, | Triage Stage: Accepted
feature |
Has patch: 1 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by collinanderson):

* cc: cmawebsite@… (added)

--
Ticket URL: <https://code.djangoproject.com/ticket/5253#comment:24>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,

Jun 5, 2015, 9:11:12 AM6/5/15

to django-...@googlegroups.com

#5253: serializer for csv format for loaddata and dumpdata
-------------------------------------+-------------------------------------
Reporter: Adam Schmideg | Owner: erob
<adam@…> |

Type: New feature | Status: closed

Component: Core | Version: master
(Serialization) |

Severity: Normal | Resolution: wontfix

Changes (by freakboy3742):

* status: new => closed
* resolution: => wontfix

Comment:

I'm going to make an executive decision and close this as a wontfix.

This specific ticket is asking for a piecemeal addition to Django's
serializers; the real underlying problem is that Django's serializers
aren't as flexible as they need to be for real world problems.

Once upon a time, I harboured dreams of writing a fully flexible
serialisation framework for Django; luckily, that is no longer required,
as Tom Christie has written a very robust and flexible set of serializers
for Django REST Framework. If we want this in Django, we should maybe
approach Tom to pull that piece of REST Framework into Django; but
frankly, I'm not convinced this is worth the code churn (and it's one more
thing that the core team doesn't have to worry about, which is a good
thing).