Changes between Initial Version and Version 2 of Ticket #18867


Ignore:
Timestamp:
Aug 28, 2012, 6:00:53 PM (12 years ago)
Author:
Russell Keith-Magee
Comment:

Historically, we haven't modified Django's docs to point out problems in downstream libraries -- the reasoning being that if the bug is fixed, there's never an action to correct Django's documentation and remove the warning. We've usually relied on the ticket tracker making it easy to find such problems.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #18867

    • Property Component Database layer (models, ORM) → Documentation
    • Property Owner changed from nobody to Aymeric Augustin
    • Property Triage Stage Unreviewed → Accepted
    • Property Type Bug → Cleanup/optimization

  • Ticket #18867 – Description

    initial v2  
    11Loading a YAML fixture with a timezone aware DateTimeField in Django 1.4 will cause the following warning even if the field is defined with timezone information in the YAML file
    2 
     2{{{
    33django/db/models/fields/__init__.py:808: RuntimeWarning: DateTimeField received a naive datetime (2012-08-27 13:01:56.784734) while time zone support is active.
    4 
     4}}}
    55Excerpt from testdata.yaml
    6 
     6{{{
    77[...] , insert_date: !!timestamp '2012-08-27 13:01:56.784734+00:00', [...]
    8 
     8}}}
    99The test data is loaded by adding "fixtures = ['testdata']" at the start of a test case class.
    1010
Back to Top