I think we need to carefully consider the side-effects of merging a new python-django. Debian sid is now at 1.10 and it's caused quite a bit of breakage. It looks like a number of upstream projects are not updated wrt django 1.10 feature changes. One example is horizon, see Thomas' patches here: https://anonscm.debian.org/cgit/openstack/horizon.git/log/?h=debian/newton
Other packages that have required patches are: django-classy-tags django-nose python-django-babel python-django-bootstrap-form python-django-formtools python-django-openstack-auth python-django-sekizai python-django-appconf python-django-babel python-django-bootstrap-form python-django-compressor python-django-formtools python-django-openstack-auth python-django-overextends python-django-pyscss.
I think we need to carefully consider the side-effects of merging a new python-django. Debian sid is now at 1.10 and it's caused quite a bit of breakage. It looks like a number of upstream projects are not updated wrt django 1.10 feature changes. One example is horizon, see Thomas' patches here: https:/ /anonscm. debian. org/cgit/ openstack/ horizon. git/log/ ?h=debian/ newton
Other packages that have required patches are: django-classy-tags django-nose python-django-babel python- django- bootstrap- form python- django- formtools python- django- openstack- auth python- django- sekizai python- django- appconf python-django-babel python- django- bootstrap- form python- django- compressor python- django- formtools python- django- openstack- auth python- django- overextends python- django- pyscss.