"long int..." exception reported with strange traceback location

Joe Peterson joe at skyrush.com
Tue Jul 5 06:42:10 CEST 2005


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"
----------------

This way, there's no "float" call, simply an asignment of a long int...

	Thanks, Joe


Peter Otten wrote:
> Terry Reedy wrote:
> 
> 
>>>>>os.utime("foo_test_file", (0, float(sys.maxint+1)))
>>
>>Traceback (most recent call last):
>>File "<stdin>", 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* a tuple. So a least the error message is wrong, too.
> 
> Peter
> 



More information about the Python-list mailing list