On 11/09/2016 03:13 AM, Stephen Finucane wrote: > 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. We are building up a Python 3.4 stack on EPEL 6 & 7, so that is an option. I'm also poking at Python 2.7 on EPEL6 here: https://copr.fedorainfracloud.org/coprs/g/python/python2.7_epel6/packages/ Anyone in the python sig group and build there and play along/help out. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion@xxxxxxxx Boulder, CO 80301 http://www.nwra.com _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
