[Python-Dev] float atime/mtime/ctime - a bad idea? (original) (raw)
Guido van Rossum guido@python.org
Wed, 16 Oct 2002 11:41:41 -0400
- 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 ]
With Guido's most recent suggestion (put ints into the tuple), it is even more likely that nothing will break if floats are activated (we should investigate the two known incidents to find out whether they were using the tuple interface).
I was using the tuple interface -- this code needed to work under Python 2.1.
I completely agree about reflexes and general feelings. However, we assume that this indeed won't matter in practice.
Amen.
--Guido van Rossum (home page: http://www.python.org/~guido/)
- 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 ]