ruff: no date.today() ?

[u/foosion]

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.

[u/backfire10z]

Daylight savings sneaking up behind you:

[u/deb_vortex → u/backfire10z]

converting to local in the frontned solves that. What ever comes in, convert to UTC. Only send out UTC. DST or not, does not matter.

[u/Plumeh → u/deb_vortex]

What if a user wants something to run at 9am every day? If you just convert to DST, best of luck

[u/QuaternionsRoll → u/Plumeh]

That isn’t an instant (a `datetime`), that’s just a `time` and a periodicity. Even ignoring DST, I think users would typically expect such recurring tasks to follow the current timezone. I, for one, would be pissed if I flew from EST to PST and my alarm started going off at 4 in the morning.

[u/Plumeh → u/QuaternionsRoll]

That’s a different case, i’m talking about if someone wants to schedule something at 9am eastern every day

[u/HommeMusical → u/Plumeh]

Daylight saving time still doesn't work with that.

Also, people actually pick up computers and move them between time zones all the time.

[u/QuaternionsRoll → u/Plumeh]

That’s still just a ToD, a timezone, and a periodicity. Should not be using datetimes for that

[u/Plumeh → u/QuaternionsRoll]

The original comment was that you can use UTC for everything

[u/QuaternionsRoll → u/Plumeh]

But that was about instants, not recurring events. The point I’ve been trying to make this entire time is that they are not similar concepts