cronekorkn/left4me
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

spec(tz-aware-datetime): correct speculative l4d2host carve-out

Browse source 
The previous version implied l4d2host has tz patterns to defer. An
inventory grep showed it has no datetime usage at all (no `from datetime`
import anywhere in the tree). Replace the bullet with the verified
finding.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
mwiegand 2026-05-16 13:01:25 +02:00
parent 18113637e9
commit 0c552082dc
No known key found for this signature in database
1 changed files with 3 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
docs/superpowers/specs/2026-05-16-tz-aware-datetime-design.md
View file

@ -238,8 +238,9 @@ datetimes all along, just losing the tzinfo on the wire.
- Postgres portability. `UtcDateTime` would adapt with `impl = - Postgres portability. `UtcDateTime` would adapt with `impl =
DateTime(timezone=True)` if the dialect supports it, but switching DateTime(timezone=True)` if the dialect supports it, but switching
dialects is its own project. dialects is its own project.
- Cleanup of any tz patterns in `l4d2host` (the dedicated-server side of - `l4d2host` (the dedicated-server CLI side of the repo) has no datetime
the repo). This work touches only `l4d2web`. usage — no `from datetime` import anywhere in the tree, verified by
grep. The scope boundary is documentary; no follow-up work exists.
- Static enforcement (mypy plugin, ruff rule) for "naive datetime crossing - Static enforcement (mypy plugin, ruff rule) for "naive datetime crossing
into a `UtcDateTime` column." The runtime `TypeError` is the gate; a into a `UtcDateTime` column." The runtime `TypeError` is the gate; a
static check would be a nice-to-have. static check would be a nice-to-have.