2017-12-06 10:26 GMT+01:00 Matthias Runge <mrunge@xxxxxxxxxxxxxxxxx>: > On Wed, Dec 06, 2017 at 09:56:28AM +0100, Lumir Balhar wrote: >> On 12/05/2017 04:27 PM, Miro Hrončok wrote: >> > Maybe a Fedora Change coordinating this would be nice? > > probably a good idea. > >> > Those are packages that require python(2)-django and are themselves not >> > prefixed with python(2)-django: >> > >> > cobbler-web >> > fts-monitoring >> > gramps-webapp >> > graphite-web >> > kobo-admin >> > kobo-django >> > kobo-hub >> > pony >> > pulp-server >> > >> > I suggest we go trough them and see. At least the kobo thing is probably >> > being ported to 3 by Lumír (CC'ed) > > graphite-web requires Django <= 1.11.99, but has been ported to python3. > >> Kobo is currently tested with Django 1.6 and 1.8. The codebase is ported to >> Python 3 but it needs to be modified to support Django >= 1.11. There are >> some issues but I don't know Django well enough to fix them. >> >> I am not a maintainer nor a user of Kobo but I think that Kobo will need >> python2-django in Fedora. >> > >> > Even if we and up having python2-django, I suggest we remove all the >> > unneeded python2-django-wahtnots anyway and only keep the ones used by >> > the apps. > Yes, this makes sense. > > Going the safe route, we should add the python2 package based on > django-1.11.x and current apps would continue to work. > > Thoughts? cobbler-web would benefit from using such python2-django. (I have a pending PR upstream to support current django-1.xx). Thx -- - Nicolas (kwizart) _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
