[issue13866] {urllib, urllib.parse}.urlencode should not use quote_plus

2012-02-23 Thread Stephen Day
Stephen Day stevv...@gmail.com added the comment: While it's likely that adding a `quote`/`quote_plus` function paramater to urlencode is the right solution, I want to ensure that the key point is communicated clearly: encoding a space as a '+' is pathological, in that in the common case

[issue13866] {urllib, urllib.parse}.urlencode should not use quote_plus

2012-02-13 Thread Stephen Day
Stephen Day stevv...@gmail.com added the comment: I apologize for reopening this bug, but I find your interpretation to be inaccurate. While technically valid, the combination of the documentation, the function name and the main use cases yields pathological invocations of urlencode. My bug

[issue13866] {urllib, urllib.parse}.urlencode should not use quote_plus

2012-01-25 Thread Stephen Day
New submission from Stephen Day stevv...@gmail.com: The current behavior of the urlencode function (2.7: urllib, 3.x: urllib.parse) encodes spaces as pluses: from urllib import urlencode urlencode({'a': 'some param'}) 'a=some+param' However, in most instances, it would be desirable

[issue5183] wsgiref.simple_server not working

2009-02-07 Thread Stephen Day
New submission from Stephen Day stephen.h@gmail.com: The attached application doesn't work. I think the value of self.headers (see line 114) has a blank line at the end that it did not in Python 2.5 Here is the error message that occurs when it gets a request (http://127.0.0.1:8080

[issue5183] wsgiref.simple_server not working

2009-02-07 Thread Stephen Day
Stephen Day stephen.h@gmail.com added the comment: This seems to be fixed already (see Issue4718). Next time I'll search more... ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5183