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
>
> Not going to carry this on much more as I doubt I'll be convincing. And
while I, for the most part, agree that group pledges won't change the minds
of those locked to 2.7, I'm hopelessly optimistic about it :-).
And how exactly can that help Django?
>
I think anything which advances and promo
The 1.11 release note already tell clearly it will be the last version
of django supporting python2.
2016-07-10 16:17 GMT+02:00 Sam Willis :
> As far as I can tell the only place where Django's Python 2.x deprecation is
> stated is here https://www.djangoproject.com/weblog/2015/jun/25/roadmap/
>
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 o
As far as I can tell the only place where Django's Python 2.x deprecation is
stated is here https://www.djangoproject.com/weblog/2015/jun/25/roadmap/
I think it should be more prominently stated in the docs, and as 1.11 is
supposedly the last to support 2.7 (according to the blog post) it may be
On my phone so excuse typos.
On Sun, 10 Jul 2016, 13:28 Florian Apolloner, 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
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
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 c
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
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 p
10 matches
Mail list logo
