[Python-Dev] float atime/mtime/ctime - a bad idea? (original) (raw)

Kevin Jacobs jacobs@penguin.theopalgroup.com
Wed, 16 Oct 2002 09:44:27 -0400 (EDT)

On 16 Oct 2002, Martin v. Loewis wrote:

Guido van Rossum <guido@python.org> writes:

> In this particular case, I think having a global flag should be good > enough. We can easily rig the standard library not to depend on its > value. Sounds good. Unless I hear otherwise, I'll add statfloattimes(bool).

Please don't! The global setting isn't sufficient since many of us access many 3rd party modules. Why not simply create properies that return the int/float versions from the same structure and store the float versions? That seems to be an instant win for all use-cases.

My 2e-2cents, -Kevin

--

Kevin Jacobs The OPAL Group - Enterprise Systems Architect Voice: (216) 986-0710 x 19 E-mail: jacobs@theopalgroup.com Fax: (216) 986-0714 WWW: http://www.theopalgroup.com