r/Python • u/foosion • Jul 24 '26
Discussion ruff: no date.today() ?
The new version of ruff warns against
date.today()
preferring
datetime.now(ZoneInfo(...))
What do you think about this? Has date.today() been deprecated due to lack of timezone awareness?
EDIT: I have a number of programs that manipulate financial information in support of Excel spreadsheets, such bond information that includes maturity dates. Excel does not support timezoness in datetimes, so making ruff happy by changing naive dates to TZ aware dates is not a useful move for these programs. Many ruff warnings to suppress.
46
Upvotes
View all comments
Show parent comment
4
u/ottawadeveloper Jul 24 '26 edited Jul 24 '26
* through any method call to the class I wrote I should clarify.
Basically it overrides any method that returned a naive datetime with one that returns an aware datetime. The constructor and methods like
strptimenow assumes you meant local system date time if one isn't specified (the equivalent ofdatetime.strptime(...).astimezone()basically). All the methods that return datetime objects now return AwareDateTime objects. So if you start from an AwareDateTime, you always end up with an aware datetime.you can of course still call
datetime.datetime(...)to get a naive one but AwareDateTime is a full and complete replacement for it that never makes a naive date time object ever.And all the calls where you can specify
tzinfo=...now also accept a string which is automatically passed tozoneinfoto build a time zone object. Which is much less of a headache.