[Python-bugs-list] [Bug #110709] bug in time.sleep (PR#65)

[noreply@sourceforge.net]

Bug #110709, was updated on 2000-Jul-31 14:30
Here is a current snapshot of the bug.

Project: Python
Category: None
Status: Closed
Resolution: None
Bug Group: Platform-specific
Priority: 5
Summary: bug in time.sleep (PR#65)

Details: Jitterbug-Id: 65
Submitted-By: Dave Dula <ddula@darkroom.cx>
Date: Wed, 25 Aug 1999 20:18:25 -0400 (EDT)
Version: None
OS: None

>>Full_Name: David Dula
>>Version: 152c1
>>OS: Debian Alpha Linux (potato) 2.2.1
>>Submission from: client42207.atl.mediaone.net (24.88.42.207)


>>his is a interesting bug that seems to have started after I upgraded to debian
>>potato from slink.

>>It must be a library related bug but this report might help somebody
>>troubleshoot.

>>At first I thought it was a bug in threading because it prevented the solaris
>>hack sleep from returning
>>thus my thread.start() never returned.

>>But further digging show that

>>import time
>>time.sleep(0.1) # will always hang on on this platform

>>Work around is to always sleep at least one second - I will do some more looking
>>at the time class when I get a chance.

This code shows it is the library that is broken.

int main()
{
printf("%f\n",floor(0.100000));
}

returns 36028797018963968.000000

So floor is broken. not a python bug sorry.

I guess something is up with libm

Dave Dula
*--------------------------------------------------------------------------
Dave Dula 
ddula@atl.mediaone.net
http://www.darkroom.cx
Despite the cost of living, have you noticed how 
popular it remains?


====================================================================
Audit trail:
Mon Aug 30 12:35:54 1999	guido	moved from incoming to platformbug
Mon Aug 30 12:36:23 1999	guido	changed notes

Follow-Ups:

Date: 2000-Aug-25 10:46
By: jhylton

Comment:
Dave Dula writes:

My further digging show that it wasn't a bug with python really but the bug
was that floor returned a very large number that caused sleep to 'hang'

So I believed it either to be a kernel bug or a bug in libm but regardless
I have just confirmed that on potato running 2.2.16 the problem no longer seems
to exist so I think the bug can be closed out as a library bug that is now
fixed

-------------------------------------------------------

For detailed info, follow this link:
http://sourceforge.net/bugs/?func=detailbug&bug_id=110709&group_id=5470