[issue34215] streams.py:IncompleteReadError is message is unclear when expected is None

2019-05-17 Thread Tyler Bell
Tyler Bell added the comment: I've updated my PR to reflect a better message for the IncompleteReadError exception. When expected is None, the error reads, "IncompleteReadError: 1 bytes read on a total of None expected bytes" which is confusing. My PR changes this to "In

[issue34215] streams.py:readuntil IncompleteReadError is message is incorrect

2018-07-24 Thread Tyler Bell
New submission from Tyler Bell : This may have already been cleared as I opened the PR months ago But the gist is that the Exception is misleading and the test is incorrect. -- components: Library (Lib) messages: 322329 nosy: mrbell...@gmail.com priority: normal pull_requests: 7975