Le dimanche 13 juin 2021 à 01:09:26 UTC+2, re...@fleschenberg.net a écrit :
> 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. > I understand this concern. I wonder if that could be solved separately, for example by: - returning int subclasses from AutoField's to_python (a bit like str/SafeString for handling escaping) - not localizing those integers, unless use_l10n is forced (True) Does this look like a plan (even without touching USE_L10N)? On 6/11/21 6:50 PM, Claude Paroz wrote: > > Is there a possible deprecation path? > Maybe add a system check that warns if the setting is still present? Sure, the warning could suggest some tips or redirect to some part of the docs. Thanks for the input. 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/cf8b1556-551c-45b0-889b-2ccf885acab3n%40googlegroups.com.
