We noticed the same thing. Sooner or later, you may need to use timestamps to determine the order or sequence in which events occurred. (E.g., to settle a dispute.) To that end, you are right to standardize on a single time zone. But it’s also important to eliminate Daylight Saving effects.
Not so long ago, thanks to DST, we had a morning with two separate times named “01:30”. Which came first? Will your database entries tell you? Reliably?
To avoid this problem, we are standardizing on UTC. It is unaffected by DST. I suspect that Server Modules use UTC.
Docs say
Any naive datetime.datetime objects that are transferred between client and server (or vice versa) will have a timezone explicitly set before being sent. When leaving the server, they will be set to UTC, and when leaving the client they will be set to the timezone of the user’s browser.
class datetime.datetime
A combination of a date and a time. Attributes: year, month, day, hour, minute, second, microsecond, and tzinfo.
So you should be able to convert all of them to UTC – or to whatever standard you choose.