diff --git a/docs/howto/initial-data.txt b/docs/howto/initial-data.txt index fcfecc82a1d..4ec2b0bae3b 100644 --- a/docs/howto/initial-data.txt +++ b/docs/howto/initial-data.txt @@ -30,7 +30,7 @@ Or, you can write fixtures by hand; fixtures can be written as JSON, XML or YAML ` has more details about each of these supported :ref:`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 look like in JSON: diff --git a/docs/topics/serialization.txt b/docs/topics/serialization.txt index c3ef1558bfd..fba5113e405 100644 --- a/docs/topics/serialization.txt +++ b/docs/topics/serialization.txt @@ -165,7 +165,7 @@ Identifier Information ========== ============================================================== .. _json: https://json.org/ -.. _PyYAML: https://www.pyyaml.org/ +.. _PyYAML: https://pyyaml.org/ XML --- diff --git a/tests/timezones/tests.py b/tests/timezones/tests.py index 0119bbe06db..42be78ae25c 100644 --- a/tests/timezones/tests.py +++ b/tests/timezones/tests.py @@ -607,7 +607,7 @@ class SerializationTests(SimpleTestCase): # - JSON supports only milliseconds, microseconds will be truncated. # - PyYAML dumps the UTC offset correctly for timezone-aware datetimes, # 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. def assert_python_contains_datetime(self, objects, dt):