[Web-SIG] WebOb

Tres Seaver tseaver at palladion.com
Tue Oct 23 16:14:47 CEST 2007

Hash: SHA1

Guido van Rossum wrote:
> 2007/10/22, Ian Bicking <ianb at colorstudy.com>:
>> I redid the front page to make it more brief: http://pythonpaste.org/webob/
> Much better; I'll try to review it in more detail later. Right now a
> few details jump off the page to me: GET and POST are verbs and IMO
> poor names for what they represent;

Just MHO:  I don't find them that confusing.  Would names like
'GET_data' and 'POST_data' be clearer?  Coming from Zope land, I'm not
used to caring about the distinction between GET and POST (for purposes
of examining the parameters passed in the request), so I'd probably use
'params' instead.

> params is usually called query (isn't it?);

Depends on what you mean by "usually":  in Zope, this is called 'form',
and it represents either the parsed query string (for GET requests) or
the parsed form data from the payload (for POST requests).

> and what's the advantage of using Request.blank() instead
> of simply Request()?

'blank' represents an unusual case:  fabricating a request object
without having a WSGI-compliant environment dict already in hand.  I
kind of like simplifying the "mainline" case (__init__ doesn't have to
sniff whether you passed an environment or not:  you get a TypeError if
you try).

- --
Tres Seaver          +1 540-429-0999          tseaver at palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


More information about the Web-SIG mailing list