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

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

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

• 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 ]

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