Sorry to jump in here at the end, but just wanted to put a word in.

The extra dependencies are due to the fact that pyramid integrates a lot of
other very good packages. This IS a GOOD thing, not bad. It makes pyramid
better and those other packages better because there are more "stakeholders"
in those packages.

Think about all the neat features Django has and how no other web framework
is able to reuse it. It's a shame it's like this, not a sign of a well
designed framework(don't get me wrong, I think Django is VERY good).

Now I know there isn't a lot of reusable bits that Pyramid uses, really only
Chameleon, Webob, Mako and Paste, but it's not a full-stack framework like
Django is. I assume TurboGears, once integrated with Pyramid, will integrate
a lot of the other web-framwork related packages(ie forms, web helpers, ORM,
etc).

IMO, entertaining this notion is a waste of time. I enjoy all the decoupled
packages the repoze/pyramid project creates--it's a sign of some really
great development. Pyramid is taking a different route than other frameworks
do, maybe better(it's all opinions..).

I do feel for beginners who don't know what to do about authentication and
authorization--I know I at first got hung up on that. I think pyramid could
ship with a sane authtkt, acl, basic auth, htpasswd enabled setup so
beginners starting don't have to think about it. Even though, providing your
own authentication integration is trivial really and almost always depends
on your database selection and authorization requirements.... Or maybe just
include something basic in all the templates...


-Nathan

On Fri, Mar 4, 2011 at 11:55 AM, Reed L O'Brien <reedobr...@gmail.com>wrote:

> On Mar 4, 2011, at 12:39 PM, Chris McDonough wrote:
>
> > On Fri, 2011-03-04 at 04:43 -0800, Andrey Petrov wrote:
> >> Re: Excessive dependencies.
> >
> >
> > Of these, the only ones to very easily *not* install would be Mako,
> > Chameleon, PasteScript, Paste, and PasteDeploy.  The others are core
> > dependencies that really can't very easily be externalized.
> >
> > Doing that would take us down to 13 dependencies.  We could indeed make
> > "pyramid_chameleon" and "pyramid_mako" and "pyramid_paste" packages to
> > restore the functionality for users of those dependencies.
> >
> > Would that actually service any particular goal?
>
> no
>
> > Would having fewer "rails" in the core actually make anybody happier?
>
> no
>
> Sincerely,
> anybody
>
> >
> > - C
>
> --
> You received this message because you are subscribed to the Google Groups
> "pylons-devel" group.
> To post to this group, send email to pylons-devel@googlegroups.com.
> To unsubscribe from this group, send email to
> pylons-devel+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/pylons-devel?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-devel" group.
To post to this group, send email to pylons-devel@googlegroups.com.
To unsubscribe from this group, send email to 
pylons-devel+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/pylons-devel?hl=en.

Reply via email to