Roundup Robot devnull@devnull added the comment:
New changeset e7c62e0981c7 by Senthil Kumaran in branch 'default':
Fix closed Issue #11968 - the start_response header values in wsgiref shoudl be
http://hg.python.org/cpython/rev/e7c62e0981c7
--
nosy: +python-dev
Changes by Senthil Kumaran sent...@uthcode.com:
--
resolution: - fixed
stage: needs patch - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11968
___
Roundup Robot devnull@devnull added the comment:
New changeset 5add0c01933f by Senthil Kumaran in branch '3.2':
Issue #11968 - the start_response header values in wsgiref shoudl be str not
http://hg.python.org/cpython/rev/5add0c01933f
New changeset 482f60d6a687 by Senthil Kumaran in branch
Changes by Éric Araujo mer...@netwok.org:
--
nosy: +skrah
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11968
___
___
Python-bugs-list mailing
Phillip J. Eby p...@telecommunity.com added the comment:
Yes, the 'b' is a docs error.
I previously removed this in:
http://hg.python.org/cpython-fullhistory/rev/2697326d4a77
It appears to have been reverted during a merge, here:
Éric Araujo mer...@netwok.org added the comment:
Thanks for the report. Can you tell more about the bug you perceive? The doc
and code for wsgiref were carefully updated to play well with Python 3 clean
bytes/characters distinction, so I’m surprised by this bug report. Maybe you
mistakenly
Terry J. Reedy tjre...@udel.edu added the comment:
Takayuki is correct, the status and header strings should, it seems, be 'native
strings', not bytes.
The experimental proof is to run the current example code (I did so from IDLE
editor window on WinXP) and then enter http://localhost:8000/
New submission from Takayuki SHIMIZUKAWA shimizuk...@gmail.com:
WSGI sapmle code at wsgiref document
(http://docs.python.org/py3k/library/wsgiref.html#wsgiref.util.setup_testing_defaults)
was broken.
- status = b'200 OK'
- headers = [(b'Content-type', b'text/plain; charset=utf-8')]
+ status
