On 12.12.2017 16:52, Nicolas Chauvet wrote:
> 2017-12-12 16:17 GMT+01:00 Miro Hrončok <mhroncok(a)redhat.com>:
>> On 7.12.2017 10:56, Matthias Runge wrote:
>>> To follow-up on this, I'm drafting a change. Since my
>>> responsibilities changed, this has a quite low priority for me.
>>> Any help is greatly appreciated!
>>>  https://fedoraproject.org/wiki/User:Mrunge/Django20
> It would be more simple to introduce a separate python2-django given
> this package namespace is free.
We are aware of that and we are deliberately not doing that.
See the motivation in Detailed Description .
Note that providing it is our contingency plan .
> It would just need to be bump at version-release: 1.11.5-2.fc28
> because python(2)-django sub-package in f27 is currently at 1.11.5-1
> This could even be introduced in epel7 (if python is recent enought
> there, but then this is a separate issue).
For those of you, who are not following the main devel list so closely,
this might be important for Python SIG:
-------- Forwarded Message --------
Subject: Django 2.0 released, and what it means to you
Date: Tue, 5 Dec 2017 09:19:39 +0100
From: Matthias Runge <mrunge(a)matthias-runge.de>
tl;dr if you're not maintaining/using a Django related package,
you can safely skip this message.
Django 2.0 was released quite recently. While it is mostly compatible with
earlier versions, the SIGNIFICANT change is, to drop support for Python 2.
I'm intending to update Django in Rawhide to 2.0 in 2 weeks. If you're
maintaining a package depending on Django, please make sure to disable
the python2 subpackage. Please keep in mind, you'll also need proper
If there is any bug, blocker, whatever connected to this change,
please make also sure to report it in bugzilla and
make your bug a blocker for.
Matthias Runge <mrunge(a)matthias-runge.de>