#23832: Storage API should provide a timezone aware approach
-------------------------------------+-------------------------------------
     Reporter:  jaylett              |                    Owner:
         Type:  New feature          |                   Status:  new
    Component:  File                 |                  Version:  1.7
  uploads/storage                    |               Resolution:
     Severity:  Normal               |             Triage Stage:
     Keywords:                       |  Unreviewed
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  1
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by jaylett):

 I've updated the patch a little, although not to use
 `datetime.utcfromtimestamp` as yet. Bit stumped by the code in
 `tests.staticfiles_tests.storage` which doesn't look like it's capable of
 testing what the comment says it's for, but is the remaining place that
 would need updating. (The tests still pass if I update the custom Storage
 backend in there, making me think that there's a test lying around that
 isn't really testing what it should be — the existing code should throw an
 exception.)

 Not going to take this further until there's consensus on the approach we
 want to take.

--
Ticket URL: <https://code.djangoproject.com/ticket/23832#comment:10>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.de44004b154cd6c3c1c457aa461ce1dd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to