#5268: add yaml save_dump argument
---------------------------------+------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: jacob
Status: new | Component: Serialization
Version: SVN | Resolution:
Keywords: | Stage: Unreviewed
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
---------------------------------+------------------------------------------
Changes (by russellm):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
Configurability is great, but is there any compelling reason that we
shouldn't just change the implementation to use safe_dump all the time?
I'm not a YAML expert, but looking at the PyYAML docs, it appears that the
only place the difference would matter is when serializing 'arbitrary
Python objects'. I don't think we need this capability, and if we are, we
should be able to work around it without too much difficulty.
--
Ticket URL: <http://code.djangoproject.com/ticket/5268#comment:1>
Django Code <http://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 post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
