[issue14652] Better error messages for wsgiref validator failures

2015-02-13 Thread Berker Peksag
Berker Peksag added the comment: Here is an updated patch. For InputWrapper.read(), see issue 18610. -- nosy: +berker.peksag stage: - patch review versions: +Python 3.4, Python 3.5 -Python 3.3 Added file: http://bugs.python.org/file38131/issue14652.diff

[issue14652] Better error messages for wsgiref validator failures

2012-05-17 Thread Sidney San Martín
Sidney San Martín s...@sidneysm.com added the comment: Thanks Jeff, I’m actually a relatively new Python developer and got the impression that it was best practice to always use a tuple for string formatting, for consistency. Here’s an updated patch which drops the tuples for those cases.

[issue14652] Better error messages for wsgiref validator failures

2012-05-16 Thread Jeff McNeil
Jeff McNeil j...@jmcneil.net added the comment: I went through the patch real quick and I noticed that your using single element tuples in your string formatting. That makes sense in situations where the argument might itself be a tuple, however, not on calls to len() as that will return an

[issue14652] Better error messages for wsgiref validator failures

2012-04-23 Thread Sidney San Martín
New submission from Sidney San Martín s...@sidneysm.com: wsgiref’s validation middleware is missing messages for many of its assertions, and its docstring doesn’t reflect read() now requiring an argument (said that it took an optional argument). Here’s a patch to add some and update the