Compare aware datetimes only after choosing time zones

An aware datetime includes a UTC offset, so it can identify an instant. For a comparison that is easy to inspect and log, first choose UTC as the common zone and call astimezone(timezone.utc) on both values. The example starts with 09:00 at UTC−04:00 and 14:30 UTC. Conversion makes their actual instants explicit: 13:00 UTC and 14:30 UTC, so the first is earlier.

The assertions check this particular conversion and ordering; they do not validate that an external timestamp was labelled with the correct time zone. Attaching a tzinfo to a naive wall-clock value is an interpretation decision, not a conversion. Determine that zone from the data contract before constructing the aware value. Do not mix naive and aware datetimes in ordering logic: a naive value has no unambiguous position on the UTC timeline.

This uses datetime, timedelta, timezone, datetime.astimezone(), and datetime.isoformat() from the standard library. Fixed-offset timezone is sufficient for the synthetic example, but it does not model historical offset or daylight-saving rules; use a rule-based zone where the business meaning requires one. astimezone() is available in supported modern Python versions; this example works on Python 3.6+.

Read the Python datetime documentation for aware objects, UTC offsets, and conversion behavior.

AI-assistance disclosure: This article was drafted with AI assistance and should be reviewed in its application context.

from datetime import datetime, timedelta, timezone

left = datetime(2026, 5, 1, 9, 0, tzinfo=timezone(timedelta(hours=-4)))
right = datetime(2026, 5, 1, 14, 30, tzinfo=timezone.utc)

left_utc = left.astimezone(timezone.utc)
right_utc = right.astimezone(timezone.utc)

assert left_utc < right_utc
assert left_utc.isoformat() == "2026-05-01T13:00:00+00:00"

print(left_utc.isoformat())
print(right_utc.isoformat())
print(left_utc < right_utc)
2026-05-01T13:00:00+00:00
2026-05-01T14:30:00+00:00
True

Comments

Post a Comment

Popular posts from this blog

Compare Two Text Files in Python Without Modifying Them

Batu Lab Notes · Batu When comparing two versions of a configuration or notes file, “are they the same?” is only the first question. The bytes may be identical, the visible text may be equal despite different line endings, or the content may contain a real change. For small UTF-8 text files, Python’s standard library can show these distinctions without writing to either input. Quick answer For small, stable UTF-8 files, read bounded bytes, compare them first, then decode and produce a bounded unified diff. Decide explicitly whether newline differences matter. Keep both inputs read-only and review the diff for private data before sharing it. Set a limit before reading Loading an input of unknown size directly into memory is a poor default. This example checks both sizes with Path.stat() , then performs a bounded read and applies a 256 KiB limit per file. It rejects directories and other non-regular paths. If reading raises OSError , the result includes the exception ty...
Read more

Seven CSV Quality Checks to Run Before Importing Data

Batu Lab Notes · Batu A CSV file is not ready for import merely because it opens. The wrong delimiter can collapse an entire row into one column. An unexpected encoding can damage non-ASCII characters. A repeated identifier can overwrite an existing record in the destination. A short, read-only check makes these problems visible before data reaches a spreadsheet or application. Quick answer Before importing a CSV, set its encoding and delimiter, validate the exact header and every row width, distinguish empty IDs, duplicate IDs, and duplicate rows, and keep the check read-only. 1. Specify the encoding Python may open a text file with the platform’s default encoding, which can differ across machines. If the expected encoding is UTF-8, encoding="utf-8-sig" is a practical choice: it reads ordinary UTF-8 and skips an optional UTF-8 byte order mark at the start. If decoding fails, verify the source application’s export settings instead of silently trying unrelat...
Read more

Explain why SQLite transactions cannot make an HTTP call atomic

Direct answer A SQLite transaction can atomically commit database statements handled by that connection. It cannot include an HTTP service in the same commit protocol. The example commits an outbox row first, then simulates a network failure. The durable row remains pending , which is exactly the information a later delivery worker needs instead of pretending both actions succeeded or failed together. The edge case is failure after the database commit but before remote acknowledgement. Retrying then requires an idempotency design owned by the remote endpoint or a stable request key; it is not supplied by SQLite’s COMMIT . Conversely, sending the request before storing a durable intent can leave no local evidence when the process stops. This demonstration intentionally does not make an HTTP request, implement an outbox dispatcher, or prove delivery exactly once. It shows the boundary that must be designed around. Use transactions to protect the local state transition, and test remote...
Read more