I am the primary author of repoze.who. I'm currently using it in
customer projects. There are currently four contributors to it,
including myself.
As with any project, it's difficult to know where it will end up, but
I think we're off to a pretty good start, as repoze.who ships with a
good num
I am the primary author of repoze.who. There are four contributors
currently including myself. I am using the software in my own
customers' projects.
As with any project. it's hard to know where it will end up, but I
think we're in pretty good shape now as there have already been some
plugins c
This is likely relevant to all the above discussion:
http://docs.repoze.org/plugin/
and:
http://svn.repoze.org/repoze.plugin/trunk/
At least its my best shot at creating something like the ZCA without
most of the baggage (no interfaces, no XML).
--~--~-~--~~~---~-
You might want to take a look at the (still-being-revised)
http://docs.pylonshq.com/#faq for the general FAQ. There should be an
announcement up very soon. It probably won't have much more info than
that has.
For the fear of no-controllers, see:
-
http://docs.pylonshq.com/pyramid/dev/designdef
On Nov 5, 5:34 am, daniel wrote:
> had a quick look at pyramid ... too complex to me and not really
> understand for which benefits, which could not be handled with the
> lovely pylons ..
More specific criticism would be helpful.
> I feel should consider whether it's time for me to step back to
On Nov 5, 5:44 am, chrism wrote:
> > I feel should consider whether it's time for me to step back to
> > django .. I always hated zope (useless ?) complexity and I love simple
> > way of thinking
>
> I've spent ten years using Zope. Pyramid is not Zope. It
On Nov 5, 7:15 am, daniel wrote:
> No criticism at all, although it would be nice getting the relevant
> user's benefits of the change. The complexity I talked about as well
> the allergy to zope is a personal perception I would wish expressing
> here (perhaps I'm the only one feeling that, then j
On Nov 5, 3:55 pm, Mike Orr wrote:
> Less confrontation, Chris, please. Pylons users are legitimately
> concerned about any sudden changes in the API, abandonment of
> previously-supported versions, and over-Zopeification. Also, Pyramid
> is being introduced to them in a haphazard way, rather than
