[Python-Dev] float atime/mtime/ctime - a bad idea? (original) (raw)
Martin v. Loewis martin@v.loewis.de
16 Oct 2002 07:57:17 +0200
- Previous message: [Python-Dev] float atime/mtime/ctime - a bad idea?
- Next message: [Python-Dev] float atime/mtime/ctime - a bad idea?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
barry@python.org (Barry A. Warsaw) writes:
+1 on the latter idea. Since the stmtime, statime, and stctime 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. fmtime, fctime, fatime, or maybe just mtime, atime, and ctime... ?
The previous suggestion was st_mtimef, st_ctimef, ...
Regards, Martin
- Previous message: [Python-Dev] float atime/mtime/ctime - a bad idea?
- Next message: [Python-Dev] float atime/mtime/ctime - a bad idea?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]