Django 1.9

[quantum5]

We are now faced with the choice of Django 1.9, latest version, and Django 1.8, long term support.

I am in favour of Django 1.9 for its new class-based Mixins, password validation, and new admin.

We might be able to remove django-suit, which seems to be stagnating, and failing as it becomes incompatible with newer packages. For example, #308 doesn't work with django-suit, fixing it would also fix #320 by extension. It would also fix #325.

Details about this latest release of django can be found in the release notes.

[WallE256]

Removing django-suit is quite a need, as changing to something like django-admin-tools or django-admin-bootstrapped should not take long. If removing django-suit solves #308 and #320, it's kind of a must.

[Xyene]

https://github.com/barszczmm/django-wpadmin

Personally, I like the Wordpress admin theme. It officially supports Django 1.7x, but an issue on it claims that just changing VERSION to 1.8.5 allowed it to run on Django 1.8 - perhaps it'd run on 1.9x with the same hack.

[quantum5]

Is it a surprise that I like it too? However, the point was getting something regularly maintained.

[quantum5]

Upgrading would prevent #308 from forcing #333 to load a separate jQuery.

[quantum5]

Django 1.9 is successfully installed. This would be an opportunity to upgrade all packages to the latest.

[WallE256]

And provide an official requirements.txt

Sent from my iPhone

On 11 Dec 2015, at 23:24, Quantum notifications@github.com wrote:

Django 1.9 is successfully installed. This would be an opportunity to upgrade all packages to the latest.

—
Reply to this email directly or view it on GitHub.

[quantum5]

A pip freeze is now provided: https://gist.github.com/quantum5/a0ca22dfc32954274142

@WallE256

[quantum5]

Upgrade is done.