#36608: dumpdata does not use custom serializers
-------------------------------------+-------------------------------------
Reporter: ksauder | Owner: (none)
Type: Uncategorized | Status: new
Component: Core (Management | Version: 5.2
commands) |
Severity: Release blocker | Resolution:
Keywords: dumpdata custom | Triage Stage:
serializers | Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Description changed by ksauder:
Old description:
> As displayed in the diff, the code was simply broken and always raised an
> exception for custom serializer formats.
New description:
As displayed in the diff, the code was simply broken and always raised an
exception for custom serializer formats.
After further investigation, this problem could also be solved by adding
'internal_use_only = False' to the classes in the example here
https://docs.djangoproject.com/en/5.2/topics/serialization/#custom-
serialization-formats. This gets around the "if format in
serializers.get_public_serializer_formats()" check, although the old code
in the diff still doesn't make sense.
--
--
Ticket URL: <https://code.djangoproject.com/ticket/36608#comment:1>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/010701993f80482b-9aada5d1-e91e-422e-bd63-0e19df35899d-000000%40eu-central-1.amazonses.com.
