Re: [Django] #35142: DATE and DATETIME settings have no effect since USE_L10N was deprecated

2024-03-19 Thread Django 
#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 Natalia Bidart):

 * cc: Claude Paroz (added)

Comment:

 I missed this ticket yesterday when triaging #35306 but I think they are
 the same issue (documentation could benefit from some explicitness).
-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018e569a26f3-11d4018b-64e9-46ed-beed-0e0b6ddbf52b-00%40eu-central-1.amazonses.com.

Re: [Django] #35142: DATE and DATETIME settings have no effect since USE_L10N was deprecated

2024-01-25 Thread Django 
#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
-+-
Description changed by Paul:

Old description:

> Since 5.0 **USE_L10N** settings was DEPRECATED and is always True.
>
> Now settings like **DATE_FORMAT**, **DATETIME_FORMAT**,
> **DATE_FORMAT_INPUTS** etc.. don't work because as per documentation:
> "Note that the locale-dictated format has higher precedence and will be
> applied instead. But now locale-dictated formats are always enabled."
> Now locale-dictated formats will always have higher precedence.
>
> 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'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.

New description:

 Since 5.0 **USE_L10N** settings was DEPRECATED and is always True.

 Now settings like **DATE_FORMAT**, **DATETIME_FORMAT**,
 **DATE_FORMAT_INPUTS** etc.. don't work because as per documentation:
 "Note that the locale-dictated format has higher precedence and will be
 applied instead. But now locale-dictated formats are always enabled."
 Now locale-dictated formats will always have higher precedence.

 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'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.

 DEMO PROJECT: https://github.com/paulik123/django-demo-l10n

--
-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018d40a40d01-576d567e-bead-478a-9703-cd77fc03bbfc-00%40eu-central-1.amazonses.com.

Re: [Django] #35142: DATE and DATETIME settings have no effect since USE_L10N was deprecated

2024-01-25 Thread Django 
#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
-+-
Comment (by Paul):

 > I don't think that it's true, can you provide a sample project that
 reproduces your issue.
 I've created a demo project at https://github.com/paulik123/django-demo-
 l10n
 Just create a demo object then click edit.

 > 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.

 Yes, but not specifying that all format settings (DATE_FORMAT,
 DATETIME_FORMAT etc)  won't work if you just paste them settings.py seems
 confusing to me. I think at least a note should be added saying that to
 modify these settings you need to override formats.py


 Replying to [comment:1 Mariusz Felisiak]:
-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018d40a2ef16-502c7b68-508a-4523-a024-068971ffe40a-00%40eu-central-1.amazonses.com.

Re: [Django] #35142: DATE and DATETIME settings have no effect since USE_L10N was deprecated

2024-01-25 Thread Django 
#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: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018d40270d90-b253e462-33f9-427c-bb06-6a9f5c604fbf-00%40eu-central-1.amazonses.com.

[Django] #35142: DATE and DATETIME settings have no effect since USE_L10N was deprecated

2024-01-25 Thread Django 
#35142: DATE and DATETIME settings have no effect since USE_L10N was deprecated
-+-
   Reporter:  Paul   |  Owner:  nobody
   Type:  Bug| Status:  new
  Component: |Version:  5.0
  Uncategorized  |   Keywords:  USE_L10N,
   Severity:  Normal |  localization
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Since 5.0 **USE_L10N** settings was DEPRECATED and is always True.

 Now settings like **DATE_FORMAT**, **DATETIME_FORMAT**,
 **DATE_FORMAT_INPUTS** etc.. don't work because as per documentation:
 "Note that the locale-dictated format has higher precedence and will be
 applied instead. But now locale-dictated formats are always enabled."
 Now locale-dictated formats will always have higher precedence.

 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'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.
-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018d3ff4c548-ba7ea3bd-d2c5-4961-b7e8-c01b387060fd-00%40eu-central-1.amazonses.com.