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
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
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
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
Hi everyone,
I read through the recent archives, and I've seen some discussion on
similar topics, but not this exact topic recently, so if the solution
to these issues has already been decided, please point me to the
relevant messages. (Also, if this isn't the most appropriate list,
please let me
