[issue35747] Python threading event wait influenced by date change

2019-01-15 Thread ido k


New submission from ido k :

Happen on ubuntu 

Opening two threads - one thread alternate system date
The seconds waits for 60 seconds. joining both threads.

The execution should take at least 60 seconds. Takes less then 15 seconds.

Any work around?

--
components: Library (Lib)
files: wrong_wait_behaviour.py
messages: 333718
nosy: ido k
priority: normal
severity: normal
status: open
title: Python threading event wait influenced by date change
type: behavior
versions: Python 3.6
Added file: https://bugs.python.org/file48056/wrong_wait_behaviour.py

___
Python tracker 
<https://bugs.python.org/issue35747>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue35747] Python threading event wait influenced by date change

2019-01-15 Thread ido k


ido k  added the comment:

thanks for the comment

please look at the code.
i use wait on event for 60 seconds.
the wait timed out in less than 60 seconds... 

why this is not a bug?

--

___
Python tracker 
<https://bugs.python.org/issue35747>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue35747] Python threading event wait influenced by date change

2019-01-16 Thread ido k


ido k  added the comment:

thanks @pablogsal.

looks like duplicate of bugs.python.org/issue23428 

It seems like i cant trust the threading wait function and need to use busy 
waiting.

--
resolution:  -> duplicate

___
Python tracker 
<https://bugs.python.org/issue35747>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com