On Tue, Sep 21, 2010 at 10:57 AM, Ian Bicking <i...@colorstudy.com> wrote: > On Tue, Sep 21, 2010 at 12:09 PM, P.J. Eby <p...@telecommunity.com> wrote: >> >> The Python 3 specific changes are to use: >> >> * ``bytes`` for I/O streams in both directions >> * ``str`` for environ keys and values >> * ``bytes`` for arguments to start_response() and write() > > This is the only thing that seems odd to me -- it seems like the response > should be symmetric with the request, and the request in this case uses str > for headers (status being header-like), and bytes for the body.
FWIW I agree with Ian about the symmetry breaking being odd. For IronPython, most .NET webservers expect the status and headers as strings, which in .NET are unicode, but that would just be an implementation convenience for me. - Jeff _______________________________________________ Web-SIG mailing list Web-SIG@python.org Web SIG: http://www.python.org/sigs/web-sig Unsubscribe: http://mail.python.org/mailman/options/web-sig/archive%40mail-archive.com
