[Python-Dev] float atime/mtime/ctime - a bad idea? (original) (raw)
Skip Montanaro skip@pobox.com
Thu, 17 Oct 2002 13:42:48 -0500
- 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 ]
BAW> Provide different field names for float values, e.g. f_mtime,
BAW> f_ctime, f_atime, or maybe just mtime, atime, and ctime... ?
Martin> The previous suggestion was st_mtimef, st_ctimef, ...Why not simply provide an alternative method, os.fstat()? Seems cleaner to me. The field names are hard enough to remember as it is...
Skip
- 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 ]