Barry Warsaw <ba...@debian.org> writes: > For libraries that already support 2 and 3, I don't think we necessarily need > to actively drop Python 2 yet. We have great tools, so it's usually just as > easy to continue supporting both. I'm on the fence for new library packages, > but I suppose if it's also just as easy to support both, we might as well go > through NEW for both, since it's easier to drop binary packages than add them.
It is perhaps worth noting that Django 2.0 is due to be released in December: https://www.djangoproject.com/weblog/2015/jun/25/roadmap/ It will require Python >= 3.5 - that is no support for Python 2.x. https://docs.djangoproject.com/en/dev/releases/2.0/ -- Brian May <b...@debian.org>
