Hi zigo and horizon plugin maintainers, Horizon itself already supports Django 2.0 and horizon unit test covers Django 2.0 with Python 3.5.
A question to all is whether we change the upper bound of Django from <2.0 to <2.1. My proposal is to bump the upper bound of Django to <2.1 in Rocky-2. (Note that Django 1.11 will continue to be used for python 2.7 environment.) There are several points we should consider: - If we change it in global-requirements.txt, it means Django 2.0 will be used for python3.5 environment. - Not a small number of horizon plugins still do not support Django 2.0, so bumping the upper bound to <2.1 will break their py35 tests. - From my experience of Django 2.0 support in some plugins, the required changes are relatively simple like [1]. I created an etherpad page to track Django 2.0 support in horizon plugins. https://etherpad.openstack.org/p/django20-support I proposed Django 2.0 support patches to several projects which I think are major. # Do not blame me if I don't cover your project :) Thought? Thanks, Akihiro [1] https://review.openstack.org/#/c/566476/ 2018年5月8日(火) 17:45 Thomas Goirand <[email protected]>: > Hi, > > It has been decided that, in Debian, we'll switch to Django 2.0 after > Buster will be released. Buster is to be frozen next February. This > means that we have roughly one more year before Django 1.x goes away. > > Hopefully, Horizon will be ready for it, right? > > Hoping this helps, > Cheers, > > Thomas Goirand (zigo) > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
