Donald could probably provide more information, but this post from April shows the Python 3.2 numbers downloading from PyPI are constant, and pretty small [https://caremad.io/2015/04/a-year-of-pypi-downloads/] His take was that CI systems (like Django's!) were doing most of the Python 3.2 package downloading.
On Thu, Dec 3, 2015 at 2:18 PM, Josh Smeaton <josh.smea...@gmail.com> wrote: > I agree with Tim. Unless someone puts their hand up to say they definitely > require python 3.2 support for 1.8, I think it makes sense to drop support > in the next dot release of 1.8. 3.2 isn't an easy python to find in the > wild as far as I know, so I'd be surprised if there was any real support > for it on 1.8 by users. > > On Friday, 4 December 2015 02:50:24 UTC+11, Tim Graham wrote: >> >> No, using pypy3 doesn't make things easier. There are a handful of test >> failures with pypy3 and it doesn't solve the issue that >> unittest-xml-reporting doesn't work with Python 3.2. >> >> Issues aside, the main thing I'm trying to find out is, are we providing >> any substantial value supporting Django on an unsupported version of >> Python? So far no one has indicated "yes". If you care about Django >> security updates, shouldn't you care about Python security updates too? >> >> On Wednesday, December 2, 2015 at 5:22:46 PM UTC-5, Shai Berger wrote: >>> >>> On Wednesday 02 December 2015 21:05:00 Tim Graham wrote: >>> > >>> > Given that no one reading this indicated that they plan a long-term >>> > deployment of Python 3.2, how about if in the next 1.8.x release we >>> > advertise that Python 3.2 support for Django 1.8 will end January 1, >>> 2017? >>> > (we won't break anything intentionally after that, but we won't have >>> to >>> > worry about testing and can spin down our 12.04 machine before it's >>> EOL a >>> > few months later) >>> > >>> >>> Since you brought the issue up yourself -- shouldn't we "swap" PyPy3 for >>> Python 3.2? Would that make running tests on ubuntu 14.04 easier? >>> >>> Just a half-baked thought, >>> >>> Shai. >>> >> -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/0a0631c3-4733-46fc-8884-c4050c8b8701%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/0a0631c3-4733-46fc-8884-c4050c8b8701%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAJYyoGFpJ7VCfODUy9QRf%3DNBjw_XbBLxn02PVmdNZV_bdiy4qg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
