On Fri, Jul 16, 2010 at 6:20 PM, Chris McDonough <chr...@plope.com> wrote:
> > What are the concrete problems you envision with text request headers, > > text (URL-quoted) path, and text response status and headers? > > Documentation is the main reason. For example, the documentation for > making sense of path_info segments in a WSGI that used unicodey-strings > would, as I understand it, read something like this: > Nah, not nearly that hard: path_info = urllib.parse.unquote_to_bytes(environ['wsgi.raw_path_info']).decode('UTF-8') I don't see the problem? If you want to distinguish %2f from /, then you'll do it slightly differently, like: path_parts = [ urllib.parse.unquote_to_bytes(p).decode('UTF-8') for p in environ['wsgi.raw_path_info'].split('/')] This second recipe is impossible to do currently with WSGI. So... before jumping to conclusions, what's the hard part with using text? -- Ian Bicking | http://blog.ianbicking.org
_______________________________________________ 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