#35142: DATE and DATETIME settings have no effect since USE_L10N was deprecated
-------------------------------------+-------------------------------------
Reporter: Paul | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: | Version: 5.0
Internationalization |
Severity: Normal | Resolution: needsinfo
Keywords: USE_L10N, | Triage Stage:
localization | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => needsinfo
* component: Uncategorized => Internationalization
* type: Bug => Cleanup/optimization
Comment:
> It alse breaks editing on all ModelForms which have date and datetime
fields because the input is expecting ISO format, but Django forcefully
localizes the value attribute to another format.
I don't think that it's true, can you provide a sample project that
reproduces your issue.
> I've found a solution but overriding the formats.py file using the
FORMAT_MODULE_PATH setting. I think at least the documents should make it
clear you can do that.
True, if you don't like formats provided for a language you're working
with, you can use `FORMAT_MODULE_PATH` to specify your own format
definitions. This setting is documented, I'm not sure what else are you
trying to propose.
--
Ticket URL: <https://code.djangoproject.com/ticket/35142#comment:1>
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/0107018d40270d90-b253e462-33f9-427c-bb06-6a9f5c604fbf-000000%40eu-central-1.amazonses.com.
