On 2016-11-08 18:06, Matthias Runge wrote:
On 08/11/16 16:31, Brian Bouterse wrote:
I believe the future of Django in EPEL is a topic that is being
discussed on the EPSCO meetings last week and this week (18:00 UTC on
Wednesdays in #fedora-meeting, iirc).
I'm hoping that even if a newer, 1.8 based Django package is added to
EPEL6, that the existing one named Django14 can be kept for legacy
usage. The Django14 package having that unconventional name would
allow
a new package to use the more conventional python-django name which is
convenient.
I believe I can shed a light here:
- Django14 followed the old Django naming scheme in Fedora. Django was
renamed to python-django there.
- Django-1.4 was the old long term supported version and works with
pythons up to python 2.6
- Django14 should be retired IMO
I agree. It's rather decrepit at this point.
- Django-1.8 (current long term supported version) requires python 2.7.
That means, we can not have a recent Django in EPEL6 with system
python.
Per the docs [1]
Django 1.8 requires Python 2.7, 3.2, 3.3, 3.4, or 3.5
EPEL 7 comes with Python 3.4, correct? If so, 'python3-django' seems
like a thing that can be done.
- The main reason not updating to Django-1.8 in EPEL7 is reviewboard.
(I
don't know the state of askbot currently, Fedora has
ask.fedoraproject.org).
Yes, so Django 1.6 [2] is the one currently provided on EPEL 7. However,
that's Python 2.7. Would it be possible to add a Python 3 version using
Django 1.8? Alternatively (and this might be heresy), what's the
possibility of bundling that version of Django in the Reviewboard
package only, or renaming it to something like 'python-django-rb', to
free up the 'python-django' namespace for Django 1.8?
- Maintaining a django version, which was retired upstream becomes more
and more a pain, esp. if it's not part of your job to keep it alive.
Yes, that's understandable. However, the Django project does seem to
have a handle on this now with their LTS releases. Supporting only these
LTS versions seems like a good move. Once Django 1.11 is released, we
can wait a month or two for packages to upgrade their dependencies
before switching to that, and so on.
Stephen
[1] https://docs.djangoproject.com/en/1.10/releases/1.8/
[2] https://dl.fedoraproject.org/pub/epel/7/x86_64/p/
_______________________________________________
epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
