Hi, On 6/11/21 6:50 PM, Claude Paroz wrote: > As usual, the main drawback is backwards compatibility. The possibly > affected projects are those having USE_L10N = False, along with multiple > LANGUAGES. > > Is this a good idea? > I would also like to get opinions here about the compatibility issues. > Are they acceptable? > Is there a possible deprecation path?
I have run into bugs because template authors forgot to unlocalize values, in particular database IDs. These bugs often go unnoticed for quite a while because they only show up once you reach 1000 database rows. Forgetting to localize a value would typically be a much more obvious bug. So far, I have always fixed these issues by adding the unlocalize filter, though I did ponder using USE_L10N = False in the past. I don't know how many projects there are in the wild that go with USE_L10N = False. Personally, I believe removing the setting and **not** localizing values unless explicitly requested would be the best option in the long run. But I guess that would create much bigger compatibility issues. Overall, I'm +0 on this. -- René -- 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/a3b281a1-a7c0-73b8-6d7d-6e89c7d8e50a%40fleschenberg.net.
