[Django] #30733: Make datetime timezone conversion notices more consistent

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

[Django] #30733: Make datetime timezone conversion notices more consistent

Django
#30733: Make datetime timezone conversion notices more consistent
------------------------------------------------+------------------------
               Reporter:  Andrew Williams       |          Owner:  nobody
                   Type:  Cleanup/optimization  |         Status:  new
              Component:  Documentation         |        Version:  2.2
               Severity:  Normal                |       Keywords:
           Triage Stage:  Unreviewed            |      Has patch:  1
    Needs documentation:  0                     |    Needs tests:  0
Patch needs improvement:  0                     |  Easy pickings:  0
                  UI/UX:  0                     |
------------------------------------------------+------------------------
 In the QuerySet documentation, many of the APIs that work on datetime
 fields have a variation of the same notice indicating that when the USE_TZ
 setting is set to True, the database is used to do timezone conversions.
 It'd be worth replacing these with the most helpful of the variations.

--
Ticket URL: <https://code.djangoproject.com/ticket/30733>
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/051.dd39498fd54bfed4fae385d1c5b0cee8%40djangoproject.com.
Reply | Threaded
Open this post in threaded view
|

Re: [Django] #30733: Make datetime timezone conversion notices more consistent

Django
#30733: Make datetime timezone conversion notices more consistent
-------------------------------------+-------------------------------------
     Reporter:  Andrew Williams      |                    Owner:  Andrew
         Type:                       |  Williams
  Cleanup/optimization               |                   Status:  assigned
    Component:  Documentation        |                  Version:  2.2
     Severity:  Normal               |               Resolution:
     Keywords:                       |             Triage Stage:
                                     |  Unreviewed
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Andrew Williams):

 * owner:  nobody => Andrew Williams
 * status:  new => assigned


Old description:

> In the QuerySet documentation, many of the APIs that work on datetime
> fields have a variation of the same notice indicating that when the
> USE_TZ setting is set to True, the database is used to do timezone
> conversions.  It'd be worth replacing these with the most helpful of the
> variations.

New description:

 In the QuerySet documentation, many of the APIs that work on datetime
 fields have a variation of the same notice indicating that when the USE_TZ
 setting is set to True, the database is used to do timezone conversions.
 It'd be worth replacing these with the most helpful of the variations.

 Pull Request: https://github.com/django/django/pull/11718

--

--
Ticket URL: <https://code.djangoproject.com/ticket/30733#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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/066.2d0a292b33ddea706157b7cd6a895b20%40djangoproject.com.
Reply | Threaded
Open this post in threaded view
|

Re: [Django] #30733: Document that datetime lookups require time zone definitions in the database. (was: Make datetime timezone conversion notices more consistent)

Django
In reply to this post by Django
#30733: Document that datetime lookups require time zone definitions in the
database.
-------------------------------------+-------------------------------------
     Reporter:  Andrew Williams      |                    Owner:  Andrew
         Type:                       |  Williams
  Cleanup/optimization               |                   Status:  assigned
    Component:  Documentation        |                  Version:  2.2
     Severity:  Normal               |               Resolution:
     Keywords:                       |             Triage Stage:  Accepted
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by felixxm):

 * stage:  Unreviewed => Accepted


--
Ticket URL: <https://code.djangoproject.com/ticket/30733#comment:2>
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/066.2584fa24588430a95c217dbc7ac06cd8%40djangoproject.com.
Reply | Threaded
Open this post in threaded view
|

Re: [Django] #30733: Document that datetime lookups require time zone definitions in the database.

Django
In reply to this post by Django
#30733: Document that datetime lookups require time zone definitions in the
database.
-------------------------------------+-------------------------------------
     Reporter:  Andrew Williams      |                    Owner:  Andrew
         Type:                       |  Williams
  Cleanup/optimization               |                   Status:  closed
    Component:  Documentation        |                  Version:  2.2
     Severity:  Normal               |               Resolution:  fixed
     Keywords:                       |             Triage Stage:  Accepted
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"29adcd215f80383f00d9f837311e857142319722" 29adcd2]:
 {{{
 #!CommitTicketReference repository=""
 revision="29adcd215f80383f00d9f837311e857142319722"
 Fixed #30733 -- Doc'd that datetime lookups require time zone definitions
 in the database.

 Note was missing for date, year, iso_year, week, time, hour, minute,
 and second lookups.
 }}}

--
Ticket URL: <https://code.djangoproject.com/ticket/30733#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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/066.f910e30f7cd1926d5357d7532d5cc66f%40djangoproject.com.
Reply | Threaded
Open this post in threaded view
|

Re: [Django] #30733: Document that datetime lookups require time zone definitions in the database.

Django
In reply to this post by Django
#30733: Document that datetime lookups require time zone definitions in the
database.
-------------------------------------+-------------------------------------
     Reporter:  Andrew Williams      |                    Owner:  Andrew
         Type:                       |  Williams
  Cleanup/optimization               |                   Status:  closed
    Component:  Documentation        |                  Version:  2.2
     Severity:  Normal               |               Resolution:  fixed
     Keywords:                       |             Triage Stage:  Accepted
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by Mariusz Felisiak <felisiak.mariusz@…>):

 In [changeset:"16e5e8ff5a8c8eb5bfd5de999b22803819c6881e" 16e5e8ff]:
 {{{
 #!CommitTicketReference repository=""
 revision="16e5e8ff5a8c8eb5bfd5de999b22803819c6881e"
 [2.2.x] Fixed #30733 -- Doc'd that datetime lookups require time zone
 definitions in the database.

 Note was missing for date, year, iso_year, week, time, hour, minute,
 and second lookups.

 Backport of 29adcd215f80383f00d9f837311e857142319722 from master
 }}}

--
Ticket URL: <https://code.djangoproject.com/ticket/30733#comment:4>
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/066.edf06577df05d587d5c90f0a6793e1f9%40djangoproject.com.