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:49:44 -0400 |
| commit | 6a316423df349e2cbc0a4188c55d0639aa2e15c5 (patch) | |
| tree | 84bb8ce899fa0c4b0190955a7635a02f3944a8e9 /docs/intro | |
| parent | 8f8dc830dfeb321b0de3325a8d2c859fdc20c3af (diff) | |
Documented known Python 3.5+ test failures in contributing tutorial.
Diffstat (limited to 'docs/intro')
| -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 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 |