Regarding "forcing", the statement has a similar sentiment: "Third parties may offer paid support for our projects on old Python versions for longer than we support them ourselves. We won’t obstruct this, and it is a core principle of free and open source software that this is possible." If Blue Hat has a market for and chooses to develop Django 1.12 to run on their Python 2.8, that's fantastic. Just that you can't expect *free* support by the community beyond 2020.
Yes, the statement is status-quo for Django, but my motivation is more for this to expand the scope of said statement beyond the SciPy stack. Because this doesn't alter policy, I'm hoping for this as a smooth segue towards broader awareness/adoption. On Sunday, July 10, 2016 at 1:18:56 PM UTC-4, Florian Apolloner wrote: > > On Sunday, July 10, 2016 at 3:22:47 PM UTC+2, Nick Sarbicki wrote: >> >> The problem with announcing way back is people outside of the sphere >> forget. >> > > But then again those will not bother if Django is on Python3 or not. For > those it might be way more important if the default python is python3 on > their machines, or if a recent python is even available (looking at you > RHEL ;)). > > >> 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. >> > > Yeah, given the current political situation I'd rather not continue that > argument -- lets leave politics out ;) > > >> 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. >> > > And those people are not convinced by a pledge either, so whats the point. > Then again, the decisions on companies often depend on other factors (ie > support on their machines etc…), and using python3 should be evaluated on a > project per project basis (and if a [non-binding]pledge is enough to shift > your managers, you probably have something else to worry about :D). > > 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. >> > > Those people are quite aware that python3 is out there and ready, such a > statement is not going to help. It is probably quite a bit of work to > upgrade all those tutorials and they maybe do not see the gain in time vs > money or whatever… > > >> If that changes 3.x can get a big push forward. And that in the future >> can help Django. >> > > And how exactly can that help Django? > > >> Realistically though, what is stopping us from signing? What negative >> outcome can it have? >> > > Probably nothing, but Django in the past has never tried to convince > anyone or force anyone to do something (aside from the decisions we make > within our framework), and we do not feel the urge to force our view on > others -- nor sign a pledge for that matter. Our stance on Python 3 is > clear, we made our point, but we do not need or have to convince anyone > else. > > Cheers, > Florian > >> -- 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/968d26e0-d792-4e0d-8bc7-b2173e850f30%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
