A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2015-July/140954.html below:

[Python-Dev] Status on PEP-431 Timezones

[Python-Dev] Status on PEP-431 Timezones [Python-Dev] Status on PEP-431 TimezonesLennart Regebro regebro at gmail.com
Mon Jul 27 08:20:51 CEST 2015
On Mon, Jul 27, 2015 at 12:15 AM, Paul Moore <p.f.moore at gmail.com> wrote:
> I think the current naive semantics are useful and should not be
> discarded lightly. At an absolute minimum, there should be a clear,
> documented way to get the current semantics under any changed
> implementation.
>
> As an example, consider an alarm clock. I want it to go off at 7am
> each morning. I'd feel completely justified in writing tomorrows_alarm
> = todays_alarm + timedelta(days=1).

That's a calendar operation made with a timedelta. The "days"
attribute here is indeed confusing as it doesn't mean 1 day, it means
24 hours.

//Lennart
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4