[Twisted-web] Re: [Nevow-commits] r3904 - server-side (fragment) nesting, and convenience descriptor generator

Andrea Arcangeli andrea at cpushare.com
Thu Jan 12 06:43:56 MST 2006

On Thu, Jan 12, 2006 at 02:11:23PM +0100, Valentino Volonghi wrote:
> Simplifying the project. Anyway I think you are talking on 2 different levels.
> static and appserver (and others like formless IMHO) should be removed for one
> of the following 2 reasons:
> 1) No more maintained or supported (formless, although useful and different
> from forms it's currently unmaintained and should be rewritten on top of
> forms instead of the current library, this is just an example anyway).
> 2) Doesn't belong to Nevow. static, appserver, guard and others should be
> provided by the web server instead of by Nevow. It wouldn't be bad if Nevow
> only provided some default Resource subclasses (athena.LivePage and
> rend.Page) and a rendering engine with the forms package.
> Of course this is all IMHO.

formless is already a different directory isn't it? Isn't that enough?

I was talking about the repository not the directory. There's a
directory already: Nevow/nevow, Nevow/nevow is where nevow sits. I'm not
saying forms should be under the nevow directory, but in Nevow/forms.

> Looking into the future Nevow will be ported on web2 (strategy to be defined
> yet) and will drop guard, static and appserver at once for sure. IMHO we could
> also deprecate formless waiting for it to be ported over forms. The current
> formless API is already similar to forms and far from what it was in the old
> days.

Why should you obsolete formless? It's yet another package depending on
nevow. It won't get development, it won't get the latest features, but I
see no need of obsoleting it if there are project depending on them.

Backwards compatibility matters. It matters in python as much as it
metters in twisted and nevow. It's not like python provides backwards
compatibility and nevow can not.

It all depends if you're interested in growing the twisted/nevow user
base or not, if you break stuff without any good reason to break stuff,
the userbase will walk away to ruby on rails or some other project.

I'm not talking about the internals, if my cache patches breaks that's
fine, it's a feature not a bug, but if my app breaks that's annoying.

More information about the Twisted-web mailing list