#34853: [Date Input Localization] Accept-Language Header Takes Precedence Over
Language Set With Cookie
     Reporter:  blue-hexagon         |                    Owner:  nobody
         Type:  Bug                  |                   Status:  new
    Component:                       |                  Version:  4.1
  Internationalization               |
     Severity:  Normal               |               Resolution:
     Keywords:  l10n localization    |             Triage Stage:
  form input                         |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0

Comment (by blue-hexagon):

 Replying to [comment:7 Natalia Bidart]:
 > Thank you blue-hexagon for the test project, I'm cloning it right now to
 try to reproduce. While I do that, please note that when runninng
 `makemigrations` I get this warning:
 > {{{
 > book_store.Book.borrowed_from_date: (fields.W161) Fixed default value
 >         HINT: It seems you set a fixed date / time / datetime value as
 default for this field. This may not be what you want. If you want to have
 the current date as default, use `django.utils.timezone.now`
 > }}}
 > It seems that the `default` definition for `borrowed_from_date` should
 be the callable `datetime.date.today` and not the actual result of the

 Corrected it to 'timezone.now' and pushed the change.

 When testing it, please note the endpoint is:
 ****  and not the root url.

 Also note, the new repo is Django 4.2 and not 4.1 as the original ticket

Ticket URL: <https://code.djangoproject.com/ticket/34853#comment:8>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

Reply via email to