> It's puzzling why this doesn't wrap np.datetime64 instead. Or wrap boost.datetime. I don't find it that puzzling. It's meant to help deal with timezones, eff

> It's puzzling why this doesn't wrap np.datetime64 instead. Or wrap boost.datetime. I don't find it that puzzling. It's meant to help deal with timezones, efficiency isn't necessarily part of that equation. And if I were to write a simple CLI or web app I would avoid anything that would pull in a dependency like numpy or require a C-library plus its bindings. If you need to manipulate a huge amount of date times and this is something your app is constantly doing then sure, optimise for that.