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/2012-June/119854.html below:

[Python-Dev] Issue 2736: datetimes and Unix timestamps

[Python-Dev] Issue 2736: datetimes and Unix timestamps [Python-Dev] Issue 2736: datetimes and Unix timestampsDirkjan Ochtman dirkjan at ochtman.nl
Mon Jun 4 14:18:42 CEST 2012
On Mon, Jun 4, 2012 at 2:11 PM, Nick Coghlan <ncoghlan at gmail.com> wrote:
> My perspective is that if I'm dealing with strictly absolute time, I
> should only need one import: datetime
>
> If I'm dealing strictly with relative time, I should also only need
> one import: time

Can you define "relative time" here? The term makes me think of things
like timedelta.

Personally, I would really like not having to think about the time
module at all, except if I wanted to go low-level (e.g. get a Unix
timestamp from scratch).

Cheers,

Dirkjan
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