[GH-ISSUE #112] Standardize timezone handling in backend and database #81

Closed
opened 2026-02-27 19:16:47 +03:00 by kerem · 1 comment
Owner

Originally created by @EddieTheCubeHead on GitHub (Mar 5, 2024).
Original GitHub issue: https://github.com/EddieTheCubeHead/Stagnum/issues/112

There's currently a weird and uncomfortable to work with mess of aware and naive datetime objects. Standardize the mess to use only naive UTC-time objects.

Acceptance criteria: core uses ONLY naive datetime objects in UTC time.

Originally created by @EddieTheCubeHead on GitHub (Mar 5, 2024). Original GitHub issue: https://github.com/EddieTheCubeHead/Stagnum/issues/112 There's currently a weird and uncomfortable to work with mess of aware and naive datetime objects. Standardize the mess to use only naive UTC-time objects. Acceptance criteria: core uses ONLY naive datetime objects in UTC time.
kerem 2026-02-27 19:16:47 +03:00
Author
Owner

@EddieTheCubeHead commented on GitHub (Apr 10, 2024):

Done on #183

<!-- gh-comment-id:2048310218 --> @EddieTheCubeHead commented on GitHub (Apr 10, 2024): Done on #183
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Stagnum#81
No description provided.