Prepare the Django 1.9 compatibility

[dulacp]

urlpatterns should be a plain list or django.conf.urls.url instances.

As stated by the Django documentation, and Django 1.9 will probably remove it.

Cheers

[Psykopear]

Hi @dulaccc,

could you please add django 1.9 to the tests matrix to verify this incompatibility?
Furthermore, would you be interested to continue the work for django 1.9's support?
Otherwise I will continue the development from your commit.

Cheers

[dulacp]

I'll do that for the matrix

And I am very interested in continuing the django 1.9 compatibility since we will be using asap this version in our new project.
So feel free to assign it to me :) I'm working on Django 1.9 on a daily basis right now.

[dulacp]

I am fixing the errors one by one, and dropping support for the couple py26-django19 since their specify dropping support in the release notes, do you validate this choice ?

[palazzem]

Hi @dulaccc ,
actually we're working on DOT's Django versions and Python interpreters support keeping them in sync with the provided release notes. This process removes Python interpreters and early Django versions so we're sure that newer versions of DOT will work only on maintained Django versions.

In your case, it's totally fine dropping python 2.6 for Django 1.9 because it's not supported anymore; proceed leaving the rest of the test matrix as is and let us know when your PR will be ready for the community review!

Thanks again!

[dulacp]

Cristal clear !
Still some a compatibility issue to fix under python 2.6 and then it will be all green :)

But maybe we should keep this PR open until Django 1.9 hits the first release candidate I guess.

[palazzem]

It will be great having a ready to merge compatibility branch, while waiting for the official release. I think that probably it's better holding the merge, at least, for the RC1 (16 November?) because we may need intermediate milestones. @synasius what do you think about this?

Anyway, I'm also in favor of a merge (if these changes will not break any Django < 1.9) and a second double-check before any statement about our support to Django 1.9. So we can close and easily merge this PR without any (possible) future conflict.

[dulacp]

Totally agree with you, now the branch should be ready to merge, just waiting for the travis builds to show up

[synasius]

this environment can be remove since py33 support is dropped in 1.9

https://docs.djangoproject.com/en/1.8/faq/install/#what-python-version-can-i-use-with-django

[dulacp]

right, I removed it form the matrix but forgot the tox.ini file, good catch !

[dulacp]

Btw, I took the liberty to upgrade the Travis architecture with sudo: false. It improves a lot the stability of tests, especially the connection throughput for the pip install for instance.

[masci]

@dulaccc definitely a good choice moving to container-based infrastructure on Travis. 👍

[synasius]

great! we are ready to merge 👍

[dulacp]

Yeah! I will continue to keep this branch ready to merge with the next django:stable/1.9.x commits

[palazzem]

Talking with @synasius , we've decided to merge your PR now preventing merge conflicts in the future :)
Anyway, as I said before, we'll do a double check prior the next DOT release. If you want to keep your compatibility contribution (let's say, if something changes in Django 1.9), you can open a new branch / PR.

Again, thanks a lot for your contribution!

[dulacp]

Fair enough, this way everyone can keep working more freely :)

My pleasure to contribute to such a well structured project !