Dealing with dates and timezones in a python project

Question

In a side project I have to manage, compare and display dates from different formats. What's the best design strategy to follow?

I planned:

All dates are parsed according their format and stored in the db in 9-tuple python format using UTC
When I have to do calculations and compares I transform 9-tuple in datetime object (using UTC). If I have to store back some date calculation I use again 9 tuple format
On user interface time is display converting from UTC to user's timezone

Have you any feedback about this strategy?

Related question - http://stackoverflow.com/questions/2532729/daylight-saving-time-and-timezone-best-practices — Oded, Jul 26 '10 at 19:22

score 2 · Answer 1 · answered Jul 23 '10 at 16:49

2

I'd use the DB's native datetime format rather than this "9-tuple" format. It'll make queries easier, and it's probably more space-efficient too.

Shouldn't be too hard to convert from that back into a Python datetime object. You can use the dateutil module if you're having trouble.

I think you're right about keeping a consistent timezone throughout the DB though, and the convert it to the user's timezone when you need to.

answered Jul 23 '10 at 16:49

mpen

sorry it is an object database. I store directly python objects – pierocampanelli Jul 23 '10 at 16:50

1 Answers1