➜

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 neologix
Recipients ned.deily, neologix, pitrou, vstinner
Date 2015-01-28.09:26:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAH_1eM0mb46DxmMdyWbX2g4sR4g0PT0aTVB5y-eT9u93y6ZyoQ@mail.gmail.com>
In-reply-to <1422431627.99.0.846258759079.issue23285@psf.upfronthosting.co.za>
Content 
> I added a few prints to the send and receive loops of _test_send.  When running on a reasonably current Debian testing Linux:

Thanks, that's what I was suspecting, but I really don't understand
why 200ms isn't enough for a socket write to actually do something:
maybe OS-X and *BSD schedulers are large timeslice...

Could you try by increasing signal_period to e.g. 0.5, and sleep_time to 1?
History
Date User Action Args
2015-01-28 09:26:11neologixsetrecipients: + neologix, pitrou, vstinner, ned.deily
2015-01-28 09:26:11neologixlinkissue23285 messages
2015-01-28 09:26:11neologixcreate