Re: Allowing numbers in the top level domain

[Claude Paroz]

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 receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/e2587b66-b398-4b74-a17a-a4dbb4bdec29%40googlegroups.com.

Re: Adding Occitan language code 'oc' in LANG_INFO

[Yann Sionneau]

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 it's unlikely to do any harm), I'd do:


from django.conf import global_settings
LANGUAGES = global_settings.LANGUAGES + [('oc', gettext_lazy('Occitan'))]

Would you like to make a documentation PR to reword it to not just 
talk about restricting? There are many more languages in the world 
than in Django right now!


On Sun, 27 Oct 2019 at 12:34, Yann Sionneau > wrote:


Hi,

Thanks Adam for your quick answer!

I investigated this a bit more in depth.

It seems that Django cannot use any translation that the visitor
would want (via cookie or via Accept-Language header) if the
language code is not in settings.LANGUAGES.

If I read documentation about settings.LANGUAGES :
https://docs.djangoproject.com/en/2.2/ref/settings/#languages

it says :

"Generally, the default value should suffice. Only set this
setting if you want to restrict language selection to a subset of
the Django-provided languages."

So the documentation is talking about *restricting* the list, not
expanding it.

Anyway, I tried to expand it, it seemed to work.

I did this in my settings file:

LANGUAGES.append(
 ('oc',gettext_lazy('Occitan')),
)

Would you say that my understanding is correct? Is my solution
correct? The best one?

Thanks!

Yann

Le 25/10/2019 à 15:00, Adam Johnson a écrit :

Hi Yann,

I'm no translation expert, but I believe you can add your own
language codes in your project and translate your project's
strings. To be added to core django I think we need (at least
some) translation coverage. The last language added was Armenian,
in this PR: https://github.com/django/django/pull/10830 . The
translations were first submitted on Transifex:

https://docs.djangoproject.com/en/dev/internals/contributing/localizing/#translations

Thanks,

Adam

On Fri, 25 Oct 2019 at 10:47, Yann Sionneau mailto:y...@sionneau.net>> wrote:

Hello,

Do you think there would be any show stopper preventing from
adding
Occitan language in

django/conf/locale/__init__.py LANG_INFO ?

That would (I think) allow Django apps to use 'oc' translations.

Cheers,

-- 


Yann

-- 
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
django-developers+unsubscr...@googlegroups.com
.
To view this discussion on the web visit

https://groups.google.com/d/msgid/django-developers/aa5f8eb8-4ad3-e52b-16b8-38aa911a7c2e%40sionneau.net.



-- 
Adam
-- 
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 django-developers+unsubscr...@googlegroups.com
.
To view this discussion on the web visit

https://groups.google.com/d/msgid/django-developers/CAMyDDM1YDoNw1%3D21E0UpVMyvygAvJJEZrvS1wHemLvEJbf5F4Q%40mail.gmail.com

.
-- 
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 django-developers+unsubscr...@googlegroups.com
.
To view this discussion on the web visit

https://groups.google.com/d/msgid/django-developers/e20fa361-9345-fc3f-6844-b0378e81e98d%40sionneau.net

.



--
Adam
--
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 django-developers+unsubscr...@googlegroups.com 
.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAMyDDM3HwZzHKmTZm%2Bgf3%2BGVjFLOL8TQedg9yk__a0jAR

Re: Allowing numbers in the top level domain

[Aymeric Augustin]

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 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 receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/e2587b66-b398-4b74-a17a-a4dbb4bdec29%40googlegroups.com
> 
> .
>


-- 
Aymeric.

-- 
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 django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CANE-7mVF3FoQOJfubrbTfv-BY0oqRPwOr2pG%3DOxFeDH7c9%3Dv%2BQ%40mail.gmail.com.

Python version support for LTS Django (in particular v2.2)

[Carlton Gibson]

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 support. It seems that 
lots of users want both the latest 
Python and the Django LTS. 


Django 2.2 officially only supports Python 3.8. 

Python 3.8 is already available. 

Python 3.9 will be available Oct 2020, which is a ≈18months before 2.2. is 
EOL, and is roughly equivalent to when we added support for Python 3.7 to 
Django 1.11. 


I predict a similarly strong demand to support the newer Python versions in 
Django 2.2. 

I'm happy to take whatever line we deem appropriate here, but I'd like to 
avoid, for example, saying "No, it's not supported" for many months, before 
then changing our minds. 

So what shall we do? 

Django 2.2 is still in mainstream support and I think it should 
automatically get Python 3.8 support. 
I think version of Django should support the new Python versions whilst in 
mainstream support, but I think this applies doubly to the LTS, even though 
the LTS isn't my thing, simply because of the demand for it. 

Data point: I didn't test the full matrix but, tests are already passing 
here. 

For Python 3.9 I think we should probably declare now that we will review 
whether we will support it for 2.2 LTS when it's released. 
(i.e. if it's a small back port like the one required for 3.7/1.11 then 
yes, otherwise no.) 


What do we think? 

Thanks 
Kind Regards,

Carlton

-- 
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 django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/2fd6b27c-fae3-4a05-b8b7-9f04eaf3da89%40googlegroups.com.

Re: Python version support for LTS Django (in particular v2.2)

[Carlton Gibson]

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 group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/6a01c30f-3a41-4d66-b40d-c8de221a62fb%40googlegroups.com.

Re: Python version support for LTS Django (in particular v2.2)

[Tobias McNulty]

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 who was confused about this. (And thanks
Mariusz for reminding me of this page which more clearly lays out the
supported Django/Python version combos:
https://docs.djangoproject.com/en/dev/faq/install/#what-python-version-can-i-use-with-django)
:)

At least, we may wish to clarify the 2.2 release notes to say that versions
before and after those explicitly listed are NOT supported (and/or link
people to the above page from the release notes). Depending on how closely
one is paying attention (I wasn't), it's possible to read this sentence and
think that Django actually *wants *me to use Python 3.8 with Django 2.2:

"We highly recommend and only officially support the latest release of each
series." (https://docs.djangoproject.com/en/2.2/releases/2.2/)

(I think) I see now that that's referring to the latest release of *Django*
rather than *Python*, but I'm still not entirely sure about that. (The
other possibility being that that language is a holdover from the time when
we were supporting both Python 2 and 3.)

Cheers,


*Tobias McNulty*Chief Executive Officer

tob...@caktusgroup.com
www.caktusgroup.com


On Wed, Oct 30, 2019 at 10:56 AM Carlton Gibson 
wrote:

> 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 group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/6a01c30f-3a41-4d66-b40d-c8de221a62fb%40googlegroups.com
> 
> .
>

-- 
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 django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAMGFDKR8EdXd_9ZwbPK2rk1BSecFQ3bRypTOXOKZb3ajYkRB6g%40mail.gmail.com.

Re: Python version support for LTS Django (in particular v2.2)

[Carlton Gibson]

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 series. 

...

On Wednesday, 30 October 2019 16:47:15 UTC+1, Tobias McNulty wrote:
>
> 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 who was confused about this. (And thanks 
> Mariusz for reminding me of this page which more clearly lays out the 
> supported Django/Python version combos: 
> https://docs.djangoproject.com/en/dev/faq/install/#what-python-version-can-i-use-with-django)
>  
> :)
>
> At least, we may wish to clarify the 2.2 release notes to say that 
> versions before and after those explicitly listed are NOT supported (and/or 
> link people to the above page from the release notes). Depending on how 
> closely one is paying attention (I wasn't), it's possible to read this 
> sentence and think that Django actually *wants *me to use Python 3.8 with 
> Django 2.2:
>
> "We highly recommend and only officially support the latest release of 
> each series." (https://docs.djangoproject.com/en/2.2/releases/2.2/)
>
> (I think) I see now that that's referring to the latest release of 
> *Django* rather than *Python*, but I'm still not entirely sure about 
> that. (The other possibility being that that language is a holdover from 
> the time when we were supporting both Python 2 and 3.)
>
> Cheers,
>
>
> *Tobias McNulty*Chief Executive Officer
>
> tob...@caktusgroup.com 
> www.caktusgroup.com
>
>
> On Wed, Oct 30, 2019 at 10:56 AM Carlton Gibson  > wrote:
>
>> 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 group and stop receiving emails from it, send an 
>> email to django-d...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-developers/6a01c30f-3a41-4d66-b40d-c8de221a62fb%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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 django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/f02fff0d-7ffc-4a21-8d98-655742fad3c1%40googlegroups.com.

Re: Python version support for LTS Django (in particular v2.2)

[Tobias McNulty]

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 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 django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAMGFDKQipHMR5VyM-VvCx0uPB1E9DPeTOX08fL%3DwYR%2B%3D%2B7GTgw%40mail.gmail.com.

Re: Python version support for LTS Django (in particular v2.2)

[Adam Johnson]

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 only officially support the latest point
>> release of each support Python series.
>>
>
>  👏 Love it! (though perhaps drop or edit the second "support")
>
> Tobias
>
> --
> 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 django-developers+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/CAMGFDKQipHMR5VyM-VvCx0uPB1E9DPeTOX08fL%3DwYR%2B%3D%2B7GTgw%40mail.gmail.com
> 
> .
>


-- 
Adam

-- 
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 django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAMyDDM2Kx4ep6XaW8HctpvWE329OWCx%2BtCjqj%3DbLBpzUUF6HFA%40mail.gmail.com.

Re: Python version support for LTS Django (in particular v2.2)

[Nick Pope]

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 Python 3.7.

I also feel the policy was a little aggressive given that the total change 
to support Python 3.7 was 
https://github.com/django/django/compare/216398d1...c11a7b4

So +1 to Python 3.8 for Django 2.2, with an option on Python 3.9 if trivial.

On Wednesday, 30 October 2019 14:44:20 UTC, Carlton Gibson wrote:
>
> 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 support. It seems that 
> lots of users want both the latest 
> Python and the Django LTS. 
>
>
> Django 2.2 officially only supports Python 3.8. 
>
> Python 3.8 is already available. 
>
> Python 3.9 will be available Oct 2020, which is a ≈18months before 2.2. is 
> EOL, and is roughly equivalent to when we added support for Python 3.7 to 
> Django 1.11. 
>
>
> I predict a similarly strong demand to support the newer Python versions 
> in Django 2.2. 
>
> I'm happy to take whatever line we deem appropriate here, but I'd like to 
> avoid, for example, saying "No, it's not supported" for many months, before 
> then changing our minds. 
>
> So what shall we do? 
>
> Django 2.2 is still in mainstream support and I think it should 
> automatically get Python 3.8 support. 
> I think version of Django should support the new Python versions whilst in 
> mainstream support, but I think this applies doubly to the LTS, even though 
> the LTS isn't my thing, simply because of the demand for it. 
>
> Data point: I didn't test the full matrix but, tests are already passing 
> here. 
>
> For Python 3.9 I think we should probably declare now that we will review 
> whether we will support it for 2.2 LTS when it's released. 
> (i.e. if it's a small back port like the one required for 3.7/1.11 then 
> yes, otherwise no.) 
>
>
> What do we think? 
>
> Thanks 
> Kind Regards,
>
> Carlton
>
>

-- 
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 django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/613aee69-1d8b-445c-a64b-0917eed976a7%40googlegroups.com.