A Python Epoch Timestamp Timezone Trap
A Python Epoch Timestamp Timezone Trap
I primarily yell at code. Well, I look sternly in its general direction, gently urging it to do my bidding.
You're viewing a single thread.
For what it's worth, I have been a convert from naive to aware for a couple years now. I used to like to think naive == UTC, but when data comes from unverifiable sources, you can't know that for certain...
Honestly, I'm working on a system with data we control and we've been migrating pg columns from WITHOUT to WITH TIMEZONE - our server natively runs in PST rather than UTC for convenience and everytime we find a naive timestamp we have two main options to consider - whether the dev properly stored values as UTC or whether they just used a now like function and got PST.
I have to ask: does your server switch to storing PDT during daylight savings? Either way, I'm so sorry you have to deal with that.
So all of our dates should be stored in UTC... but everytime we have to deal with an unmarked column we have to check if it's in PST because a developer forgot. If a developer did forget, they'd probably grab the PDT value during DST.