On Fri, Jul 16, 2010 at 6:20 PM, Chris McDonough <span dir="ltr"><<a href="mailto:chrism@plope.com">chrism@plope.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div class="h5">
> What are the concrete problems you envision with text request headers,<br>
> text (URL-quoted) path, and text response status and headers?<br>
<br>
</div></div>Documentation is the main reason. For example, the documentation for<br>
making sense of path_info segments in a WSGI that used unicodey-strings<br>
would, as I understand it, read something like this:<br></blockquote><div><br>Nah, not nearly that hard:<br><br>path_info = urllib.parse.unquote_to_bytes(environ['wsgi.raw_path_info']).decode('UTF-8')<br>
<br>I don't see the problem? If you want to distinguish %2f from /, then you'll do it slightly differently, like:<br><br>path_parts = [<br> urllib.parse.unquote_to_bytes(p).decode('UTF-8')<br> for p in environ['wsgi.raw_path_info'].split('/')]<br>
<br>This second recipe is impossible to do currently with WSGI.<br clear="all"><br>So... before jumping to conclusions, what's the hard part with using text?<br></div></div><br>-- <br>Ian Bicking | <a href="http://blog.ianbicking.org">http://blog.ianbicking.org</a><br>