Comments on Just a little Python: Hierarchical CherryPy

I've written a decorator that does this:
http:/...

2006-03-30T14:07:00.000-05:00

I've written a decorator that does this:
http://docs.cherrypy.org/quixote

robert, thanks for the comment. The reason I can&...

2005-12-12T10:19:00.000-05:00

robert, thanks for the comment. The reason I can't use default is that I want to have CherryPy continue traversal after the "programmable" part of my path (the <customer id> in the example above). default(), on the other hand, insists on being the last thing on the path. (It handles the rest of the path as positional arguments.) If there was a mechanism to do this, you could basically have nice, dynamic paths. I guess it's kind of Zope-ish. But maybe that's not so bad.

I'd like to do the "Right" thing in CherryPy, I'm pretty sure overriding __getattr__ is not the Right thing, but I can't figure out a blessed way to do it. Of course, this is just a "wart," in my opinion. Not enough to make me switch to something else.

I tend to use CherryPy's default method and just h...

2005-12-10T19:57:00.000-05:00

I tend to use CherryPy's default method and just handle the rest of the dispatching manually.

Well, I did at least find the way Quixote does thi...

2005-12-10T13:40:00.000-05:00

Well, I did at least find the way Quixote does this: by using the _q_lookup() method. It's covered in Quixote tutorial 1.

Comments on Just a little Python: Hierarchical CherryPy

I've written a decorator that does this:http:/...

robert, thanks for the comment. The reason I can&...

I tend to use CherryPy's default method and just h...

Well, I did at least find the way Quixote does thi...

I've written a decorator that does this:
http:/...