A RetroSearch Logo

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

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2002-October/029599.html below:

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

[Python-Dev] float atime/mtime/ctime - a bad idea?Martin v. Loewis martin@v.loewis.de
16 Oct 2002 07:57:17 +0200
barry@python.org (Barry A. Warsaw) writes:

> +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... ?

The previous suggestion was st_mtimef, st_ctimef, ...

Regards,
Martin



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