On Tue, Dec 05, 2017 at 10:45:54AM +0100, Petr Viktorin wrote: > > 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 > > obsoletes. > > > > 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[1]. > > Hi, > Another option is to create a new "python2-django" package containing the > latest Django 1.x code (which is still supported upstream as LTS). That > would mean dependent packages would have until April 2020 to drop Python 2. > If that would help, let me know and I'll package it. Interesting idea, but how would you handle the mandatory python2 package for it then? Would that require some FPC decision? I would expect the python3-django would get upgraded at least a few times until 2020. Matthias -- Matthias Runge <mrunge@xxxxxxxxxxxxxxxxx> _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
