[issue1014] cgi: parse_qs and parse_qsl misbehave on empty strings

2007-09-17 Thread Guido van Rossum
Guido van Rossum added the comment: I don't see what the problem is. You requested strict_parsing=True, and this is what strict parsing does. -- resolution: -> wont fix status: open -> closed __ Tracker <[EMAIL PROTECTED]>

[issue1014] cgi: parse_qs and parse_qsl misbehave on empty strings

2007-09-17 Thread Senthil
Senthil added the comment: Hi Sean, This is a very minor issue (IMO) with Python 2.4. Why did you assign it to gvanrossum? Makes me wonder at your assignments. Thanks, Senthil __ Tracker <[EMAIL PROTECTED]>

[issue1014] cgi: parse_qs and parse_qsl misbehave on empty strings

2007-09-17 Thread Sean Reifschneider
Changes by Sean Reifschneider: -- assignee: -> gvanrossum nosy: +gvanrossum priority: -> normal __ Tracker <[EMAIL PROTECTED]> __ ___ Python-b

[issue1014] cgi: parse_qs and parse_qsl misbehave on empty strings

2007-09-06 Thread Nir Soffer
Nir Soffer added the comment: Addionally, if the default value is empty string, you expect it work with empty string. If a non empty value is needed, it would use None as the default. __ Tracker <[EMAIL PROTECTED]>

[issue1014] cgi: parse_qs and parse_qsl misbehave on empty strings

2007-08-26 Thread Senthil
Senthil added the comment: Can query strings be empty? I am unable to find an instance. -- nosy: +orsenthil __ Tracker <[EMAIL PROTECTED]> __ __

[issue1014] cgi: parse_qs and parse_qsl misbehave on empty strings

2007-08-24 Thread David Jessup
New submission from David Jessup: In Python 2.4.4, cgi.parse_qs(qs='', strict_parsing=True) errors out: Traceback (most recent call last): File "", line 1, in ? File "/usr/lib/python2.4/cgi.py", line 183, in parse_qs for name, value in parse_qsl(qs, keep_blank_values, strict_parsing):