Matt Goodall
On Sat, 2004-04-24 at 17:26, Donovan Preston wrote:
On Apr 24, 2004, at 3:34 AM, James Y Knight wrote:
Open question: does Nevow go into twisted/web/? If so, how do we handle standalone (not depending on twisted at all) nevow? Perhaps standalone nevow is just a branch of twisted/web/nevow/ with appropriate modifications? If nevow isn't a package in twisted/web, dirlist and failure can't go into twisted.web because they depend on Nevow.
Here is what I am thinking: Nevow should be a standalone package, but should also be included with twisted.web. I would prefer that nevow *not* be included in the twisted. package, but be shipped with the twisted.web tarball.
I agree that Nevow should be a standalone framework but I'm not convinced that bundling Nevow with t.web is good for either of them.
t.web (http protocol, request/resource interface, http client and http server (including vhost, ditrib, rewrite, etc)) makes a great base for web application frameworks, web services, web servers etc. Once the current limitations have been addressed I doubt there will be a great need for further releases other than bug fixing.
Could we imagine that t.web become part of standard lib of python ? -- William - http://flibuste.net