"Ben Sizer" <[EMAIL PROTECTED]> writes:
> I see what you mean, but unfortunately I think there is a lot more
> fuzziness than that. If the separate parts were clearly delineated
> things would be a lot better. I look to the Database API Specification
> as a great example of how this could (should?) be done, allowing for
> easy interchangeability while still providing a well-documented
> standard
Constant queries on c.l.python for "Which DB module should I use"
would indicate that having a standard and to many choices isn't really
better than having no standard and to many choices.
> and the opportunity to bundle a basic module with the standard
> library without raising the difficulty level for those who wish to
> use other frameworks.
Marking one web framework - or one DB module - as blessed would
certainly ease the problem. I don't have a problem with that, but I
don't build a Python distribution.
> A PyWebForm API and a PyWebSession API
> would be fairly easy to create, for example. Templating maybe less so,
> but not much.
I'm not convinced these would be fairly easy to cerate. If you think
that's the case, please take a shot at it, as I think such a standard
would be a good thing.
<mike
--
Mike Meyer <[EMAIL PROTECTED]> http://www.mired.org/home/mwm/
Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information.
--
http://mail.python.org/mailman/listinfo/python-list
