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 vxgmichel
Recipients asvetlov, vxgmichel, yselivanov
Date 2018-10-25.12:32:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1540470746.12.0.788709270274.issue35065@psf.upfronthosting.co.za>
In-reply-to
Content
I'm not sure whether it is intended or not, but I noticed a change in the  behavior of `StreamReader` between version 3.7 and 3.8.

Basically, reading some received data from a closed TCP stream using `StreamReader.read` might hang forever, under certain conditions.

I'm not sure what those conditions are but I managed to reproduce the issue consistently with the following workflow:
 - server writes some data
 - client reads a part of the data
 - client closes the writer
 - server closes the writer
 - client tries to read the remaining data

The test attached implements the behavior. It fails on 3.8 but passes on 3.7
History
Date User Action Args
2018-10-25 12:32:26vxgmichelsetrecipients: + vxgmichel, asvetlov, yselivanov
2018-10-25 12:32:26vxgmichelsetmessageid: <1540470746.12.0.788709270274.issue35065@psf.upfronthosting.co.za>
2018-10-25 12:32:25vxgmichellinkissue35065 messages
2018-10-25 12:32:25vxgmichelcreate