#35306: Localisation of dates very confusing - why can't it be turned off
anymore?
-------------------------------------+-------------------------------------
Reporter: Richard | Owner: nobody
Type: Bug | Status: new
Component: | Version: 5.0
Internationalization |
Severity: Normal | Resolution:
Keywords: LANGUAGE_CODE, | Triage Stage:
DATE_FORMAT | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Natalia Bidart):
Hello Richard, thank you for your report. I've been debugging your issue
for a few days now. I think we may need to make some docs adjustments as
you imply, but I do not think the code is broken. See as a references
[https://stackoverflow.com/questions/77654801/use-l10n-deprecated-but-it-
disables-datetime-input-formats-when-removed this post in stackoverflow].
Have you tried using the `formats.py` approach to solve your need?
--
Ticket URL: <https://code.djangoproject.com/ticket/35306#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018e51eedb49-745e6250-3e50-45b2-a559-590b3edf3804-000000%40eu-central-1.amazonses.com.
