> For a time library, the lowest building block should be the timestamp of a > single float64, not a complex calendar object. You should store timestamps > and transfer timestamps.
Yup. In units of seconds since 1/1/1970, right? Although I've sometimes worried how soon the precision will degrade, since there are 'only' 52 bits of mantissa. There are cases where you want to store a (timestamp, timezone) tuple, like for blog posts, when it's useful to know what the local time was.
