Hi Aymeric, I don't think this is a question of what it would do for Django. More what Django could do 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. Python could gain from the greater uptake of 3.x and further downstream Django will benefit too. I don't find it smug. I think it's a reality check. Nick. On Sat, 9 Jul 2016, 07:51 Aymeric Augustin, < [email protected]> wrote: > Hello Nick, > > This website was quickly discussed by a few team members some time ago. It > wasn’t clear to us what joining this initiative would achieve for Django. > > At first sight, it would mostly allow those who run on Python 3 to feel a > bit more smug and make those who are stuck on Python 2 a bit more > frustrated. > > The web community seems to be ahead of the scientific community for moving > to Python 3. By now most Django users should be aware that they have to > figure out a plan to migrate to Python 3 (or JS, or Go, etc.) I don’t think > the scientific community is there yet. > > (To be honest, I discovered recently that some high-profile members of the > Django community are still advocating to start new projects on Python 2. > I’m failing to rationalize why they give this advice, certainly because of > my biais.) > > If we consider that we’ve reached a point where we no longer need to focus > on raising awareness, I’d rather drive the migration to Python 3 with a > stick than with a carrot. There’s plenty of cool stuff to advertise :-) > > -- > Aymeric. > > On 09 Jul 2016, at 04:03, Nick Timkovich <[email protected]> wrote: > > With the release of IPython 5.0 LTS, it was mentioned as also being the > final Py2-compat release in the series with a reference to the "Python 3 > Statement" https://python3statement.github.io/ Some of the prose in it > refers to just the Scientific Stack (Numpy, Scipy, MPL, et al.), but an > issue popped up saying that it could be generalized if other projects were > to join/"sign", e.g. Django. > https://github.com/python3statement/python3statement.github.io/issues/21 > > I'm not strongly advocating one way or the other, just thought I'd bring > it up. > > 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/0460ab73-1059-49e9-be63-2716378fddca%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/0460ab73-1059-49e9-be63-2716378fddca%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 [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/7E8B9E8B-D60E-48E4-BDB5-969BC4479EDF%40polytechnique.org > <https://groups.google.com/d/msgid/django-developers/7E8B9E8B-D60E-48E4-BDB5-969BC4479EDF%40polytechnique.org?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 [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/CAGuvt91Fw%2Bayc02jyW_-8hxj1_sekJvfkuUQsi0Ft566gyZ92w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
