On my phone so excuse typos. On Sun, 10 Jul 2016, 13:28 Florian Apolloner, <[email protected]> wrote:
> > > On Saturday, July 9, 2016 at 10:26:25 PM UTC+2, Nick Sarbicki wrote: >> >> I don't think this is a question of what it would do for Django. More >> what Django could do for python. > > > We already announced (way way back), that we are dropping support for > Python 2 and outlined our plan. That is imo enough, being on a side like > python3statement.github.io does not add any value to python. > The problem with announcing way back is people outside of the sphere forget. Yes everyone working with Django should know. I know everyone in my team is very aware of the deadline. But those outside of Django forget how seriously this is being taken by the community. Even then (warning, dumb analogy coming), if I was asked to sign a petition to my government, I wouldn't refuse just because I'd already written to my MP about it. Speaking together has more power. Again, no immediate benefit to Django, but there is one for python. > The web and scientific communities are essentially the two biggest python >> communities around. If they both joined together to say "2020 is the >> deadline for us and everyone else" it could really push a lot of others to >> see how serious the need to move is now. >> > > Everyone seriously involved in Django (agencies, companies) etc are > already aware of our plans and are hopefully preparing themselves, if not, > there is little else we can do which would change their minds… > Again, in Django most definitely are. But outside of Django it's less clear. My last job as an example had a huge pure python programme that is core to the business. My manager would try to justify upgrading to 3.x but it never caught on with the seniors. They would look at the stats and see most people still using 2.7, most libraries still working in 2.7, and see the current code still running in 2.7. There's never been anything big enough to convince them. It didn't run Django so Django announcing wouldn't have any impact. But if all the major libraries announced then it might have. Even more to the point (and far worse in my mind) are the teaching websites like codecademy and learn python the hard way. They all still use python 2! And to justify it they quote employability and lack of 3.x uptake. Again if they were to have something bigger put in front of them to show how much of a dead end 2.7 is, it could push them to change. If that changes 3.x can get a big push forward. And that in the future can help Django. Realistically though, what is stopping us from signing? What negative outcome can it have? Nick. > -- 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 [email protected]. To post to this group, send email to [email protected]. 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/CAGuvt90S1oGxePdm14J-xAzT_mPmQE3dk5_F3SZubv_hRssfHw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
