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/2002-October/029611.html below:

[Python-Dev] float atime/mtime/ctime - a bad idea?

[Python-Dev] float atime/mtime/ctime - a bad idea? [Python-Dev] float atime/mtime/ctime - a bad idea?Guido van Rossum guido@python.org
Wed, 16 Oct 2002 08:29:29 -0400
> If you're suggesting a new API, why not have it return one of
> the new datetime objects ?

That would require much more changes to the user code to use the new
feature.  And in many cases a basic timestamp is just what you need --
all you usually do is comparing them, occasionally printing them, and
both are done just as easily using the int or float form.

--Guido van Rossum (home page: http://www.python.org/~guido/)



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