Yep, my thinking too. Well, maybe it's all related to the same bug
somehow. OK, I submitted a bug report, and I included a slight
modification of the test case you guys suggested:
import sys
import os
t = 2147483648L
os.utime("foo_test_file", (t, t))
print "hi"
---
Terry Reedy wrote:
os.utime("foo_test_file", (0, float(sys.maxint+1)))
> Traceback (most recent call last):
> File "", line 1, in ?
> TypeError: utime() arg 2 must be a tuple (atime, mtime)
>
> which is quite sane. So maybe bug was introduced in 2.3 which you were
> running.
But arg 2 *is*
"Michael Hoffman" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> I came up with a simpler testcase. Strangely, the exception occurs in
> the statement *following* the os.utime() call:
>
> >>> import os, sys
> >>> os.utime("foo_test_file", (0, float(sys.maxint+1)))
> >>> print "hi"
Joe Peterson wrote:
> I could not find another example of this via internet searches, so here
> it is... I am wondering if this is a python bug or otherwise. The
> first example of this happened in a larger program of mine, and the
> traceback reports the problem at the start of a "for" loop (mak
I could not find another example of this via internet searches, so here
it is... I am wondering if this is a python bug or otherwise. The
first example of this happened in a larger program of mine, and the
traceback reports the problem at the start of a "for" loop (making no
sense), but I cannot
