#12914: Use yaml faster C implementation when available
--------------------------------------+------------------------------------
Reporter: Beuc | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Core (Serialization) | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by aaugustin):
PyYAML
[https://github.com/django/django/blob/master/tests/modeltests/timezones/tests.py#L491
isn't very good with datetimes] in general. I don't like changing tests
because we can't get the output we want, but in this case, we don't have
much choice.
PyYAML's documentation helpfully states that "''there are some subtle (but
not really significant) differences between pure Python and LibYAML based
parsers and emitters''" which may include the difference we're seeing
here. I'm not sure it's worth reporting this as a bug.
Apparently PyYAML [https://bitbucket.org/xi/pyyaml/commits/all moved to
bitbucket] two weeks ago, after 18 months without any activity.
--
Ticket URL: <https://code.djangoproject.com/ticket/12914#comment:14>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
