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/cfb4a4e9-c415-4c67-8408-7440a7c314f8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
