Fixed broken links to PyYAML page.

This commit is contained in:
CHI Cheng 2018-12-27 20:48:37 +11:00 committed by Mariusz Felisiak
parent 277de22984
commit b7dbd5ff68
3 changed files with 3 additions and 3 deletions

View File

@ -30,7 +30,7 @@ Or, you can write fixtures by hand; fixtures can be written as JSON, XML or YAML
</topics/serialization>` has more details about each of these supported </topics/serialization>` has more details about each of these supported
:ref:`serialization formats <serialization-formats>`. :ref:`serialization formats <serialization-formats>`.
.. _PyYAML: https://www.pyyaml.org/ .. _PyYAML: https://pyyaml.org/
As an example, though, here's what a fixture for a simple ``Person`` model might As an example, though, here's what a fixture for a simple ``Person`` model might
look like in JSON: look like in JSON:

View File

@ -165,7 +165,7 @@ Identifier Information
========== ============================================================== ========== ==============================================================
.. _json: https://json.org/ .. _json: https://json.org/
.. _PyYAML: https://www.pyyaml.org/ .. _PyYAML: https://pyyaml.org/
XML XML
--- ---

View File

@ -607,7 +607,7 @@ class SerializationTests(SimpleTestCase):
# - JSON supports only milliseconds, microseconds will be truncated. # - JSON supports only milliseconds, microseconds will be truncated.
# - PyYAML dumps the UTC offset correctly for timezone-aware datetimes, # - PyYAML dumps the UTC offset correctly for timezone-aware datetimes,
# but when it loads this representation, it subtracts the offset and # but when it loads this representation, it subtracts the offset and
# returns a naive datetime object in UTC (https://pyyaml.org/ticket/202). # returns a naive datetime object in UTC. See ticket #18867.
# Tests are adapted to take these quirks into account. # Tests are adapted to take these quirks into account.
def assert_python_contains_datetime(self, objects, dt): def assert_python_contains_datetime(self, objects, dt):