This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author jeffr@livedata.com
Recipients jeffr@livedata.com, paul.moore, steve.dower, tim.golden, zach.ware
Date 2019-01-05.07:59:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAP5X+rfmSBFjLJ0WcdCu-4QCicMmxex7+r7-dieYPHxq8yTVrA@mail.gmail.com>
In-reply-to <1546668705.79.0.386706807304.issue35662@roundup.psfhosted.org>
Content
I did a search and couldn't find exactly this issue. This issue is about a
broken function. It is broken because it treats a timeout as a fatal error
which crashes your Python program.

I supplied a proposed fix for the function.

If there are other known issues or tests, happy to dig in.  Seems a shame
that Python 3 on Windows needs to be running on emulated condition
variables when the OS has (apparently) working actual ones.

Jeff

On Sat, Jan 5, 2019, 1:11 AM Steve Dower <report@bugs.python.org wrote:

>
> Steve Dower <steve.dower@python.org> added the comment:
>
> There's an existing issue for this somewhere - we've tried a couple times
> to switch over and run into various issues. I'm not in a place to find it
> right now, but worth looking.
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue35662>
> _______________________________________
>
History
Date User Action Args
2019-01-05 07:59:15jeffr@livedata.comsetrecipients: + jeffr@livedata.com, paul.moore, tim.golden, zach.ware, steve.dower
2019-01-05 07:59:13jeffr@livedata.comlinkissue35662 messages
2019-01-05 07:59:13jeffr@livedata.comcreate