* Fred L. Drake, Jr. [EMAIL PROTECTED] [2007-06-16 01:06:59]:
* Coding question: Without retyping the bunch of code again in the
BaseResult, would is the possible to call parse_qs/parse_qsl function on
self.query and provide the result? Basically, what would be a good of
doing it.
* Fred L. Drake, Jr. [EMAIL PROTECTED] [2007-06-13 22:42:21]:
I see no reason to incorporate the URL splitting into the function; the
existing function signatures for cgi.parse_qs and cgi.parse_qsl are
sufficient.
Thanks for the comments, Fred. I understand, that having the signatures of
On Saturday 16 June 2007, O.R.Senthil Kumaran wrote:
The urlparse will cotain parse_qs and parse_qsl takes the query string
(not url) and with optional arguments keep_blank_values and strict_parsing
(same as cgi).
http://deadbeefbabe.org/paste/5154
Looks good.
It may be convenient
a) import cgi and call cgi module's query_ps. [circular imports]
or
b) Implement a stand alone query parsing facility in urlparse *AS IN*
cgi module.
Assuming (b), please remove the (code for the) parsing from the cgi
module, and just import it back from urlparse (or urllib). Since cgi
* Jim Jewett [EMAIL PROTECTED] [2007-06-13 19:27:24]:
a) import cgi and call cgi module's query_ps. [circular imports]
or
b) Implement a stand alone query parsing facility in urlparse *AS IN*
cgi module.
Assuming (b), please remove the (code for the) parsing from the cgi
On Tuesday 12 June 2007, Senthil Kumaran wrote:
This mail is a request for comments on changes to urlparse module. We
understand that urlparse returns the 'complete query' value as the query
component and does not
provide the facilities to separate the query components. User will have to
Hi all,
This mail is a request for comments on changes to urlparse module. We understand
that urlparse returns the 'complete query' value as the query
component and does not
provide the facilities to separate the query components. User will have to use
the cgi module (cgi.parse_qs) to get the
