Re: [Web-SIG] Python 3: Form data encoding issues in cgi and urllib modules

2009-04-15 Thread Miles Kaufmann
On Wed, Apr 15, 2009 at 5:23 PM, Graham Dumpleton wrote: > 2009/4/16 Miles Kaufmann : >> So: does anyone agree, or disagree, that cgi.FieldStorage should be >> changed to take byte streams, and many of the cgi and urllib.parse >> functions should become encoding-aware, preferably in time for Python

Re: [Web-SIG] Python 3: Form data encoding issues in cgi and urllib modules

2009-04-15 Thread Graham Dumpleton
2009/4/16 Miles Kaufmann : > On Sat, Apr 11, 2009 at 8:48 PM, Miles Kaufmann wrote: >> The first issue is that there doesn't seem to be a way to parse >> x-www-form-urlencoded query strings in a character set other than >> UTF-8, for example: >> >> 'premier=un&deuxi%E8me=deux' # latin-1 >> >> The u

Re: [Web-SIG] Python 3: Form data encoding issues in cgi and urllib modules

2009-04-15 Thread Miles Kaufmann
On Sat, Apr 11, 2009 at 8:48 PM, Miles Kaufmann wrote: > The first issue is that there doesn't seem to be a way to parse > x-www-form-urlencoded query strings in a character set other than > UTF-8, for example: > > 'premier=un&deuxi%E8me=deux' # latin-1 > > The urllib.parse.unquote* functions take

Re: [Web-SIG] Python 3: Form data encoding issues in cgi and urllib modules

2009-04-11 Thread Miles Kaufmann
On Sat, Apr 11, 2009 at 8:48 PM, Miles Kaufmann wrote: > ... > It's possible that the email.mime and http packages might also need > some changes made, but I haven't looked into those as much. > ... Apparently there's been some discussion on the python-dev and email-sig lists in the past couple of