http://code.google.com/p/pyxer/

Thanks again for the very cool and useful tools you wrote. Dirk

I’ve found webob both very useful and fun to use in writing simple RESTful apps. I’ve written a paster template for a simple view with webob that might be useful to some, at least for reference: https://svn.openplans.org/svn/standalone/webob_view/trunk/ This could be used or be modified to be used with a simple framework/routing system as presented in the tutorial — just have a bunch of views with a route for each == website.

I’m not sure wether you’ve read Diving into Python. The way code is commented in that book is absolutely genius. You see a big piece of code, just like yours. And below it you find a numbered explanation of every relevant line or group of lines.

I’m saying this because I had my little problems understanding what exactly your code does. Like the routing templating thing. I thought “Okay. This turns our nice routing syntax into actual regular expressions to use elsewhere. But how does he do it?”.

For __import__, you can also give the 4th argument as a list with a single empty string. This is the “context” argument, meaning it acts like from x import y, context being the x bit. Giving it an empty string makes it return the last bit of the first argument.

For example:

__import__('some.module', {}, {}, [''])

returns module, not some.

Carlo: yes, you can do that. To do it you need to pass a proxy application to req.get_response(). There’s one in WSGIProxy, in wsgiproxy.exactproxy.proxy_exact_request. So you can do:

req = Request.blank('http://pythonpaste.org')
resp = req.get_response(wsgiproxy.exactproxy.proxy_exact_request`

proxy_exact_request is named as such because it has no options, but reads the exact information the request contains (including stuff like SERVER_NAME so you can send a request not by DNS).

I’ve been playing with webob a lot lately and I gotta say that it’s great! In all my past apps, I’ve been trying to model requests/responses in a nice Pythonic and RESTful way but never quite made it, so webob is just what I’ve been looking for.

I was wondering if there was any plans on letting webob Request objects make actual HTTP calls, returning webob Responses? I wrote a wrapper class to do it, but I think it’d make sense to be part of the Request object. If it’s something you’d be open to, I’d like to contribute some code.

.Carlo

What’s wrong with module returned by __ import __()?