[Twisted-web] Unwinding the Twisted Web (a progress report)

[Christopher Armstrong]

James Y Knight wrote:
> So a few things:
> - I think we should dump woven.

We never deprecated it :-(

> - What is our compatibility story with old twisted-web? Now is a good 
> time to make a break, so I think it should be done. By that I mean, 
> new-twisted-web would not guarantee 100% backwards compatibleness with 
> the old API. If you want 100% old API, use the old code. Wrappers 
> *should* be provided for some normally called methods on 
> Resource/Request such that much of people's old code will work, if it's 
> doing normal resourcish stuff and not trying to be tricksy.
> - So, should a final release of OldTwistedWeb be done so people can keep 
> updating to newer versions of twisted core and leave old twisted web alone?

I think we should just put all backwards-compatibility code into 
twisted.web. So twisted.web will be API-compatible, and all of our BC 
code will live in Twisted. It will still require tmlabs.web (or 
whatever), and just wrap its APIs.

-- 
  Twisted | Christopher Armstrong: International Man of Twistery
   Radix  |          Release Manager,  Twisted Project
---------+           http://radix.twistedmatrix.com/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
Url : http://pyramid.twistedmatrix.com/pipermail/twisted-web/attachments/20040422/59560503/signature.bin