I do like this suggestion. I also find the current behaviour surprising.
Do you have a plan for implementation? I guess this would have to go
through the regular deprecation pathway?
On Tue, Oct 4, 2022 at 4:32 PM אורי wrote:
> Hi Shai,
>
> Actually, I think this issue is very similar to
Hi Shai,
Actually, I think this issue is very similar to what I wrote in the thread
of "Model-level validation". I have been using Django for 6 years, and I
was not aware that one can call translation.activate() with a language not
in django_settings.LANGUAGES. I was thinking this would raise an
Hello Djangonauts,
This suggestion is following from discussions of the security issue
which was resolved in today's release. In essence, the issue is that
language codes are optionally used as prefixes in URLs, and for this
use they also become part of regular expressions used by the URL
