I haven't seen any other activity on the idea if that's what you're asking.
There aren't any formal plans for Django development... the direction is
steered by the patches that people contribute.
On Sunday, July 10, 2016 at 6:32:47 PM UTC-4, Cristiano Coelho wrote:
>
> Sorry to bring this up (qu
Sorry to bring this up (quite a few years old already)
Are there any plans to bring this to life? The ticket seems to have died as
well.
It could be very useful to have actions re used on the detail view page
somehow. Right now the only option is to override the template.
--
You received this
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
Hi!,
the summary of this ticket is:
add bit shift operators (concretely '>>' and '<<') to F(), then you can
use these operators like this:
- F('somefield').bitleftshift(16)
- F('somefield').bitrightshift(16)
The discussion of this ticket went in few ways:
1) We permit these operato
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
10 matches
Mail list logo
