[issue32057] time.sleep(n) interrupted by signal

2017-11-17 Thread Bogdan Popa
Bogdan Popa added the comment: Fair enough. From reading PEP 475, it does look like that's what fixed it. Thanks Victor! -- resolution: -> wont fix stage: -> resolved status: open -> closed ___ Python tracker

[issue32057] time.sleep(n) interrupted by signal

2017-11-17 Thread STINNER Victor
STINNER Victor added the comment: I'm sorry but Python 3.4 doesn't accept bugfixes anymore. Same for Python 3.5. https://devguide.python.org/#status-of-python-branches > The following piece of code prints one line every second, as expected, on 3.6 > and 3.5 Good, at

[issue32057] time.sleep(n) interrupted by signal

2017-11-17 Thread Bogdan Popa
Bogdan Popa added the comment: I forgot to mention that I am on macOS Sierra (10.12.6) and I ran the code on Python 3.4.6, 3.5.3 and 3.6.3, respectively. -- ___ Python tracker

[issue32057] time.sleep(n) interrupted by signal

2017-11-17 Thread Bogdan Popa
New submission from Bogdan Popa : I ran into this while backporting some code from 3.6 to 3.5 and 3.4. The following piece of code prints one line every second, as expected, on 3.6 and 3.5, but it doesn't on 3.4. It looks like the signal is able to wake up the main