[Twisted-Python] shedding root

Ken Kinder ken at kenkinder.com
Thu Apr 7 00:48:02 EDT 2005

Jp Calderone wrote:

>  There's no reason to break existing deployments, or even encourage authors to switch away from their current tap plugins, if tap plugins are satisfying their requirements.  Deprecating mktap would just create a lot of unnecessary work.
>  A document explaining the capabilities and shortcomings of tap plugins and comparing these to the other options for deploying a Twisted application is a great idea.
>  Jp
The same could be said of most of the components of Twisted. Should one 
use twisted.web, or nevow? Manhole telnet or Manhole PB? Etc. I realize 
there might be some debate on use recommendations, but certainly 
consensuses could be gathered.

Some place to start would be a big graph of the Twisted project, with 
flags for each component indicating stability, documentation status, 
future deprecation, and a short sentence about pro's and con's. Most of 
this information exists for these components, but it's dispersed among 
mailing list archives, docstrings, and once in a while, actual 

Something like this would be quite valuable:

- twisted.project
  - ModuleA (Unstable) - Undocumented - Use ModuleB for future projects
  - ModuleB (Stable) - Documented


More information about the Twisted-Python mailing list