#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 django-updates+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/066.2d0a292b33ddea706157b7cd6a895b20%40djangoproject.com.