there is one implementation of twisted.web... twisted.web2 is merged, and what is not in twisted.web and is in twisted.web2 will not be used or will be merged in the future, there is no mess, you should just use twisted.web.
As someone who tried using twisted.web just a few days ago I can add that yes, twisted.web seems reasonably complete but no, it is not a reasonable choice at this point for many reasons (mostly the common twisted reasons: callback hell and insufficient documentation).
Imho the most interesting part about Tornado is not Tornado itself but the question it rubs into the face of the twisted evangelists: "Why didn't they just use the real twisted instead of re-inventing it?".
This post suggests that they have at least heard the question and, ofcourse, immediately snapped into their long-practiced denial position ("Thou shalt not question the twisted way, we haz performance!").
Only this time twisted does not outperform the newcomer, which should give them food for thought.
Imho the most interesting part about Tornado is not Tornado itself but the question it rubs into the face of the twisted evangelists: "Why didn't they just use the real twisted instead of re-inventing it?".
This post suggests that they have at least heard the question and, ofcourse, immediately snapped into their long-practiced denial position ("Thou shalt not question the twisted way, we haz performance!").
Only this time twisted does not outperform the newcomer, which should give them food for thought.