Not sure on how we'd put that into text, but something along the lines of "we will support 3.4+ as long as feasible for us to do so" -- though I do understand that this is like the same as saying: "We'll just support what we want, how long we want" :D
On Friday, January 6, 2017 at 2:33:24 PM UTC+1, Tim Graham wrote: > > So you all want to do a one time exception to our guidance of of > "Typically we will support a Python version up to and including the first > Django LTS release whose security support ends after security support for > that version of Python ends." and support Python 3.4 for how long? Or > revise the guidance? > > On Friday, January 6, 2017 at 8:16:02 AM UTC-5, Daniele Procida wrote: >> >> On Fri, Jan 6, 2017, Florian Apolloner <f.apo...@gmail.com> wrote: >> >> >In the end (in my experience), people are using Django everywhere and >> part >> >of the usage also comes from the fact that it's not that hard to deploy >> for >> >sysadmins since python is available anywhere; compiling a new Python + >> >infrastructure around it is something else again and requires a lot of >> >change requests in some companies. >> >> In practical terms it makes a big difference. Remember < >> https://groups.google.com/forum/#!topic/django-developers/qCjfOu-FPxQ/discussion>, >> >> that prompted a change of LTS policy? >> >> *Anything* that makes the transition easier is to be welcomed, and that >> doesn't just mean technically easier, it also means easier to think about >> and to talk about to project managers and clients and web project owners. >> >> Reassurance in time of change counts for a great deal. When someone gets >> to spend a day or two basking in the glory of a top item on Hacker News >> because he wrote a "Don't go to Python 3" article, there is clearly some >> reassuring to be done. >> >> If the technical cost of supporting 3.4 in Django 2.0 is not too high, I >> feel it would be valuable to have it. >> >> The actual technical justification for keeping it may be weak, but >> barriers to adoption are not always technical ones anyway, and my >> preference would be to keep them as low as possible. >> >> Daniele >> >> -- 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 https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/616e0309-0119-4269-85b0-a48e421a563a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
