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/029593.html below:

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

[Python-Dev] float atime/mtime/ctime - a bad idea?Barry A. Warsaw barry@python.org
Tue, 15 Oct 2002 22:09:47 -0400
>>>>> "GvR" == Guido van Rossum <guido@python.org> writes:

    GvR> Maybe we can introduce a variant of the stat() function that
    GvR> returns floats, or alternative field names that are only
    GvR> available when using attributes (not when using the tuple-ish
    GvR> API)?

+1 on the latter idea.  Since the st_mtime, st_atime, and st_ctime
attributes, and the tuple-ish API are documented as returning ints, I
think you shouldn't change that.  Provide different field names for
float values, e.g. f_mtime, f_ctime, f_atime, or maybe just mtime,
atime, and ctime... ?

-Barry



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