Barry Warsaw wrote: > Thanks. I've bumped that to release blocker for now. If there are any > other 'high' bugs that you want considered for 3.0.1, please make the > release blockers too, for now. I think wsgiref package needs to be fixed. For now it's totally broken. I've already found 4 issues about that: http://bugs.python.org/issue3348 http://bugs.python.org/issue3401 http://bugs.python.org/issue3795 http://bugs.python.org/issue4522 What needs to be fixed: 1. Headers handling in wsgiref.simple_server. Not so hard actually - in a few places headers expected as a list object instead of a dict. 2. wsgiref.handlers should support bytes instead of str. I think WSGI applications must return bytes as a result but we can allow Unicode strings in start_response() because the resulting encoding for headers is known and strings can be safely encoded. So the fix won't be so hard too - few asserts needs to be fixed and headers output needs to be directed through auxiliary encoding method. 3. Tests 4. Documentation examples. I can create the patch before December 24th if needed. -- Dmitry Vasiliev <dima at hlabs.spb.ru> http://hlabs.spb.ru
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4