HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
glyph
DateType
Python2023–2023
glyph / DateType

DateType

A type wrapper for the standard library `datetime` that supplies stricter checks, such as making 'datetime' not substitutable for 'date', and separating out Naive and Aware datetimes into separate, mutually-incompatible types.

2Distinct people
2Mentions
0Explicit recommenders
98GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A type wrapper for the standard library `datetime` that supplies stricter checks, such as making 'datetime' not substitutable for 'date', and separating out Naive and Aware datetimes into separate, mutually-incompatible types.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour2 dated mentions

Observed mentions: 2023-11-18 19:36:09 UTC to 2023-11-19 16:16:04 UTC.

012023-11-18 19:00:00 UTC to 2023-11-18 20:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsNov 18, 19:002023-11-18 20:00:00 UTC to 2023-11-18 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-11-18 21:00:00 UTC to 2023-11-18 22:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-11-18 22:00:00 UTC to 2023-11-18 23:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-11-18 23:00:00 UTC to 2023-11-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-11-19 00:00:00 UTC to 2023-11-19 01:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-11-19 01:00:00 UTC to 2023-11-19 02:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-11-19 02:00:00 UTC to 2023-11-19 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-11-19 03:00:00 UTC to 2023-11-19 04:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-11-19 04:00:00 UTC to 2023-11-19 05:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-11-19 05:00:00 UTC to 2023-11-19 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsNov 19, 05:002023-11-19 06:00:00 UTC to 2023-11-19 07:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-11-19 07:00:00 UTC to 2023-11-19 08:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-11-19 08:00:00 UTC to 2023-11-19 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-11-19 09:00:00 UTC to 2023-11-19 10:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-11-19 10:00:00 UTC to 2023-11-19 11:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-11-19 11:00:00 UTC to 2023-11-19 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-11-19 12:00:00 UTC to 2023-11-19 13:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-11-19 13:00:00 UTC to 2023-11-19 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-11-19 14:00:00 UTC to 2023-11-19 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-11-19 15:00:00 UTC to 2023-11-19 16:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-11-19 16:00:00 UTC to 2023-11-19 17:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsNov 19, 16:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Nov 18, 19:002023-11-18 19:00:00 UTC2023-11-18 20:00:00 UTC110
Nov 18, 20:002023-11-18 20:00:00 UTC2023-11-18 21:00:00 UTC000
Nov 18, 21:002023-11-18 21:00:00 UTC2023-11-18 22:00:00 UTC000
Nov 18, 22:002023-11-18 22:00:00 UTC2023-11-18 23:00:00 UTC000
Nov 18, 23:002023-11-18 23:00:00 UTC2023-11-19 00:00:00 UTC000
Nov 19, 00:002023-11-19 00:00:00 UTC2023-11-19 01:00:00 UTC000
Nov 19, 01:002023-11-19 01:00:00 UTC2023-11-19 02:00:00 UTC000
Nov 19, 02:002023-11-19 02:00:00 UTC2023-11-19 03:00:00 UTC000
Nov 19, 03:002023-11-19 03:00:00 UTC2023-11-19 04:00:00 UTC000
Nov 19, 04:002023-11-19 04:00:00 UTC2023-11-19 05:00:00 UTC000
Nov 19, 05:002023-11-19 05:00:00 UTC2023-11-19 06:00:00 UTC000
Nov 19, 06:002023-11-19 06:00:00 UTC2023-11-19 07:00:00 UTC000
Nov 19, 07:002023-11-19 07:00:00 UTC2023-11-19 08:00:00 UTC000
Nov 19, 08:002023-11-19 08:00:00 UTC2023-11-19 09:00:00 UTC000
Nov 19, 09:002023-11-19 09:00:00 UTC2023-11-19 10:00:00 UTC000
Nov 19, 10:002023-11-19 10:00:00 UTC2023-11-19 11:00:00 UTC000
Nov 19, 11:002023-11-19 11:00:00 UTC2023-11-19 12:00:00 UTC000
Nov 19, 12:002023-11-19 12:00:00 UTC2023-11-19 13:00:00 UTC000
Nov 19, 13:002023-11-19 13:00:00 UTC2023-11-19 14:00:00 UTC000
Nov 19, 14:002023-11-19 14:00:00 UTC2023-11-19 15:00:00 UTC000
Nov 19, 15:002023-11-19 15:00:00 UTC2023-11-19 16:00:00 UTC000
Nov 19, 16:002023-11-19 16:00:00 UTC2023-11-19 17:00:00 UTC101

What Hacker News says

2 sources
It's funny you should say this. Reading this article prompted me to future-proof a program I maintain for fun that deals with time; it had one use of utcnow, which I fixed. And then I tripped over a runtime type problem in an unrelated area of the code, despite the code being green under "mypy --strict". (and "100% coverage" from tests, except this particular exception only occured in a "# pragma: no-cover" codepath so it wasn't actually covered) It turns out that because of some core decisions about how datetime objects work, `datetime.date.today() < datetime.datetime.now()` type-checks but gives a TypeError at runtime. Oops. (cause discussed at length in https://github.com/python/mypy/issues/9015 but without action for 3 years) One solution is apparently to use `datetype` for type annotations (while continuing to use `datetime` objects
Read the rest
In datetime.utcnow() is now deprecated

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.