On Oct 21, 2005, at 12:22 AM, Matt Campbell wrote:
>
> Why is functionality from Quixote and Dulcinea being duplicated in QP?
> What does QP have to offer that Quixote and Dulcinea do not?

QP makes design decisions that Quixote and Dulcinea leave open.
This makes it easier to make new complete applications that use
Durus for persistence.   The cost is adaptability.

QP uses an htmltext-like class that is a subclass of unicode, and it
organizes the publisher and request and response instances a little
differently from Quixote.

> Given the already existing multitude of Python web frameworks,
> which is considered by many to be a Bad Thing, I'm concerned that
> the same group is now offering two frameworks.

Understood.   Our choices were, however, to suppress new ideas,
change Quixote to use new ideas, or to release them separately.
We chose door number three.

> Are Quixote and Dulcinea now deprecated, or

No.  They are both as good as ever.
Future releases of Dulcinea, however, will require QP so that
we can remove the duplication between them.

> will they continue to be developed along with QP?

Yes.