On 11/09/2016 03:21 PM, Kevin Fenzi wrote:
On Wed, 09 Nov 2016 10:13:48 +0000
Stephen Finucane <stephen@xxxxxxxxx> wrote:
..snip...
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?
I think we should have 1.8 in the name... if/when it drops out of
support and we want to move to 1.10, we can just retire 1.8 and move to
1.10 without having a specific flag day that breaks everyone using 1.8.
+1
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion@xxxxxxxxxxxxx
Boulder, CO 80301 http://www.cora.nwra.com
_______________________________________________
epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
