From 72d676bc06121611b85bb0a8966109c5ab5c09da Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Mon, 6 Jun 2016 10:49:44 -0400 Subject: [PATCH] [1.10.x] Documented known Python 3.5+ test failures in contributing tutorial. Backport of 6a316423df349e2cbc0a4188c55d0639aa2e15c5 from master --- docs/intro/contributing.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/intro/contributing.txt b/docs/intro/contributing.txt index 210a3ee57f..bba7bbe0ac 100644 --- a/docs/intro/contributing.txt +++ b/docs/intro/contributing.txt @@ -282,7 +282,9 @@ Once the tests complete, you should be greeted with a message informing you whether the test suite passed or failed. Since you haven't yet made any changes to Django's code, the entire test suite **should** pass. If you get failures or errors make sure you've followed all of the previous steps properly. See -:ref:`running-unit-tests` for more information. +:ref:`running-unit-tests` for more information. If you're using Python 3.5+, +there will be a couple failures related to deprecation warnings that you can +ignore. These failures have since been fixed in Django. Note that the latest Django trunk may not always be stable. When developing against trunk, you can check `Django's continuous integration builds`__ to