I think that the main reason for supporting Python 3.7 in Django 1.11 was
to help make things easier for those migrating from Python 2 to 3.
Python 3.8 was only released ~3 months before the Python 2 EOL, so most
people in the last year and up to the end of this year will likely migrate
to
I'm also in favour of adding 3.8 support and backporting 3.9 support
assuming it's not a huge change!
On Wed, 30 Oct 2019 at 16:39, Tobias McNulty wrote:
> On Wed, Oct 30, 2019 at 12:29 PM Carlton Gibson
> wrote:
>
>> That _highly recommend_ sentence could go:
>>
>> > We highly recommend and
On Wed, Oct 30, 2019 at 12:29 PM Carlton Gibson
wrote:
> That _highly recommend_ sentence could go:
>
> > We highly recommend and only officially support the latest point release
> of each support Python series.
>
Love it! (though perhaps drop or edit the second "support")
Tobias
--
You
Not so much prompted, as reminded. It's already on my mind... I've a lot of
"Add Python 3.8 support" in various places the last couple of weeks...
That _highly recommend_ sentence could go:
> We highly recommend and only officially support the latest point release
of each support Python
tl;dr: I'm in favor of officially supporting 3.8, if it looks like it won't
be so hard to do (and especially if doing so will result in a net decrease
in the support burden).
Long answer:
I'm not sure if this was prompted in part by my question in #django-dev...
but consider me one of the people
Sorry typo there. Should say:
> Django 2.2 officially only supports up to Python 3.7.
Otherwise the issue doesn't make sense.
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this
Hi all.
In November last year we added official Python 3.7 support to Django 1.11.
https://groups.google.com/d/topic/django-developers/H7fP5w0YU2I/discussion
This was 18 months after release, and well into the extended support
period.
There had been a long-line of requests to add that
Hello,
Also, as far as I know, the URLValidator is intended to catch common
mistakes of people typing URLs in text fields rather than to enforce
strictly a standard.
Best regards,
--
Aymeric.
Le mer. 30 oct. 2019 à 08:40, Claude Paroz a écrit :
> Hi,
>
> Could you please tell us a bit more
Thanks a lot!
Yes I think the documentation can improve a bit to make it more clear
that this extension can be done.
I'll have a look at that in the next days.
Cheers
Yann
On 10/29/19 4:48 PM, Adam Johnson wrote:
That looks good to me. To avoid mutating Django's default setting
(though
Hi,
Could you please tell us a bit more about what the specs say about numbers
in the top-level domain?
Claude
--
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
10 matches
Mail list logo
