Django 1.8 supports Python 3.5. It does raise a DeprecationWarning, which is safe to ignore. We only care about DeprecationWarnings in our own code. And it seems that Travis wants all allowed failures listed explicitly, so we do that. It should now pass again.master
|
|
||
| 40 |
|
40 |
|
| 41 |
|
41 |
|
| 42 |
|
42 |
|
| 43 |
|
|
|
|
43 |
|
|
| 44 |
|
44 |
|
| 45 |
|
|
|
|
45 |
|
|
| 46 |
|
46 |
|
| 47 |
|
|
|
| 48 |
|
|
|
|
47 |
|
|
| 49 |
|
48 |
|
| 50 |
|
|
|
| 51 |
|
|
|
| 52 |
|
|
|
|
49 |
|
|
|
50 |
|
|
|
51 |
|
|
|
52 |
|
|
|
53 |
|
|
|
54 |
|
|
|
55 |
|
|
|
56 |
|
|
| 53 |
|
57 |
|
| 54 |
|
58 |
|
| 55 |
|
59 |
|
|
|
||
| 77 |
|
77 |
|
| 78 |
|
78 |
|
| 79 |
|
79 |
|
| 80 |
|
|
|
|
80 |
|
|
| 81 |
|
81 |
|
| 82 |
|
82 |
|
| 83 |
|
83 |
|