mirror of
https://github.com/django/django.git
synced 2025-07-20 01:29:11 +00:00
[1.9.x] Documented known Python 3.5+ test failures in contributing tutorial.
Backport of 6a316423df349e2cbc0a4188c55d0639aa2e15c5 from master
This commit is contained in:
parent
307de7d9e8
commit
f78bf50adc
@ -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
|
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
|
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
|
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
|
Note that the latest Django trunk may not always be stable. When developing
|
||||||
against trunk, you can check `Django's continuous integration builds`__ to
|
against trunk, you can check `Django's continuous integration builds`__ to
|
||||||
|
Loading…
x
Reference in New Issue
Block a user