diff options
| author | Tim Graham <timograham@gmail.com> | 2016-06-06 10:49:44 -0400 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2016-06-06 10:50:45 -0400 |
| commit | f78bf50adcec216fc8071835bd9e4e249e15483d (patch) | |
| tree | 9530e19bbc1e0db7521909bea85e4f1d4dfc5f98 | |
| parent | 307de7d9e80e1148685b981eede0bd2fdbe91d46 (diff) | |
[1.9.x] Documented known Python 3.5+ test failures in contributing tutorial.
Backport of 6a316423df349e2cbc0a4188c55d0639aa2e15c5 from master
| -rw-r--r-- | docs/intro/contributing.txt | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/docs/intro/contributing.txt b/docs/intro/contributing.txt index ac06c1cae3..4a4a71a364 100644 --- a/docs/intro/contributing.txt +++ b/docs/intro/contributing.txt @@ -279,7 +279,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 |