[PhilChristensen]

that's just not true. i use web1 extensively, and it works very well, and although it's performance is not as good as apache or lighttpd when serving raw files, it's more than adequate for most web application development.

web2 was never a formally released product, and most of the stuff that was only available in web2 (such as wsgi support) have now been backported. there was some confusion about this for awhile, but that was only ever a community issue, not a code-related one.

i primarily took issue with you calling it a "mess", i still think that's a rather inaccurate statement.

[sophacles]

Specifically, from the outside looking in, exactly what you described is(was?) a mess. Last I looked it was confusing as to what I should use, what would be supported in the future, who (web or web2) had what feature, and what even worked. That was quite a while a go (like over a year). More recently, talk at pycon suggested things had not improved much, but I haven't verified that. I am open to the possibility that things have improved since I last looked, particularly given the overall quality of twisted stuff.

I still wonder tho, if this would be good to graft into twisted?