> I do actually get WSGI middleware. There are two issues: > 1) CherryPy isn't fully compatible with Paste-Deploy (which I think is > fixable, but is not yet fixed) > 2) Usability > #1 is a showstopper, but I do believe it will be fixed. #2 is not a > showstopper, but it's an important consideration.
Agreed, I hope #1 can be resolved soon, as I believe some of the changes they're remedying will also make Routes integration better. Regarding #2, I had the same thoughts. I recently re-organized the configuration for Pylons such that there's a very basic middleware config file like so: http://pylons.groovie.org/svn/trunk/pylons/templates/paster_template/+package+/config/middleware.py_tmpl It's about as basic and obvious as I could make it. Even if the developer knows nothing about middleware it would be rather easy with that layout to tell the developer how to add a new piece of middleware. > Sure. But, as I said, for important things that most people will use > those features need to fit the TurboGears style. After that, if there > are pieces that can be reasonably broken out and are useful for other > folks, then I'm all for that! That's kind of what I was afraid of. TurboGears goes to some obvious effort to re-use other projects in a rather seamless way, yet this comment seems to indicate no effort will be spent by TG developers to do the reverse... go to some effort to create re-usable parts rather than building them into TG.
