I guess we still like solar time a lot ;-) The point is, for date/time calculations, you need a numeric representation that increases strictly monotonically (an epoch time). If you introduce unpredictable modifications…
I think naive datetime would be fine, even if it resembles UTC - as long as you don't mix in a serial representation. The module documentation says, "Whether a naive object represents Coordinated Universal Time (UTC),…
No, I think pandas actually abstracts away pytz's footguns, so that's a good thing.
> pd.Timestamp is built on top of many awesome libraries ... pytz for example ;-)
I guess we still like solar time a lot ;-) The point is, for date/time calculations, you need a numeric representation that increases strictly monotonically (an epoch time). If you introduce unpredictable modifications…
I think naive datetime would be fine, even if it resembles UTC - as long as you don't mix in a serial representation. The module documentation says, "Whether a naive object represents Coordinated Universal Time (UTC),…
No, I think pandas actually abstracts away pytz's footguns, so that's a good thing.
> pd.Timestamp is built on top of many awesome libraries ... pytz for example ;-)