2018年6月3日(日) 10:56 Chuck Short :
> Hi
>
> On Sat, Jun 2, 2018 at 9:50 PM, Akihiro Motoki wrote:
>
>> Updates on Django 2.0 support.
>>
>> * 18 of 29 affected repositories now support Django 2.0
>> * 4 repositories have pending patches.
>> * 3 repositories below need help from individual project t
Hi
On Sat, Jun 2, 2018 at 9:50 PM, Akihiro Motoki wrote:
> Updates on Django 2.0 support.
>
> * 18 of 29 affected repositories now support Django 2.0
> * 4 repositories have pending patches.
> * 3 repositories below need help from individual project teams as I don't
> have actual running environ
Updates on Django 2.0 support.
* 18 of 29 affected repositories now support Django 2.0
* 4 repositories have pending patches.
* 3 repositories below need help from individual project teams as I don't
have actual running environments of them.
* heat-dashboard https://review.openstack.org/#/c/567
On 05/14/2018 03:30 PM, Akihiro Motoki wrote:
> Is Python 3 ever used for mod_wsgi? Does the WSGI setup code honor
> the variable that tells devstack to use Python 3?
>
>
> Ubuntu 16.04 provides py2 and py3 versions of mod_wsgi (libapache2-mod-wsgi
> and libapache2-mod-wsgi-py3) and as a
Excerpts from Ivan Kolodyazhny's message of 2018-05-14 22:20:42 +0300:
> Hi all,
>
> From the Horizon's perspective, it would be good to support Django 1.11 as
> long as we can since it's an LTS release [2].
> Django 2.0 support is also extremely important because of it's the first
> step in a pyt
Hi all,
>From the Horizon's perspective, it would be good to support Django 1.11 as
long as we can since it's an LTS release [2].
Django 2.0 support is also extremely important because of it's the first
step in a python3-only environment and step forward on supporting
next Django 2.2 LTS release w
2018年5月14日(月) 21:42 Doug Hellmann :
> Excerpts from Akihiro Motoki's message of 2018-05-14 18:52:55 +0900:
> > 2018年5月12日(土) 3:04 Doug Hellmann :
> >
> > > Excerpts from Akihiro Motoki's message of 2018-05-12 00:14:33 +0900:
> > > > Hi zigo and horizon plugin maintainers,
> > > >
> > > > Horizon i
Excerpts from Akihiro Motoki's message of 2018-05-14 18:52:55 +0900:
> 2018年5月12日(土) 3:04 Doug Hellmann :
>
> > Excerpts from Akihiro Motoki's message of 2018-05-12 00:14:33 +0900:
> > > Hi zigo and horizon plugin maintainers,
> > >
> > > Horizon itself already supports Django 2.0 and horizon unit
2018年5月12日(土) 3:04 Doug Hellmann :
> Excerpts from Akihiro Motoki's message of 2018-05-12 00:14:33 +0900:
> > 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
On 05/11/2018 05:14 PM, Akihiro Motoki wrote:
> 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
Excerpts from Akihiro Motoki's message of 2018-05-12 00:14:33 +0900:
> 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
>
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.
(Not
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 G
13 matches
Mail list logo
