On Thu, 2011-03-03 at 09:31 -0800, Ben Bangert wrote: > On Mar 3, 2011, at 9:28 AM, Chris McDonough wrote: > > > Sounds like (s)he is blowing off a little steam. All of these points > > are addressed in > > http://docs.pylonsproject.org/projects/pyramid/1.0/designdefense.html . > > Indeed, my comment is awaiting moderation on the blog, I cited that URL as > well. :)
I realize this blog post was mostly about letting off steam, but it bears a better response I guess: - As for "how can a 1.0 framework have deprecated classes", it's because it's not a 1.0 framework. It's a 2.0 framework renamed (repoze.bfg became Pyramid, and old repoze.bfg apps still run after automated conversion). - (S)he says "Ditch Zope. Ditch ZCML, ZODB, and traversal". Pyramid doesn't depend on either ZCML or ZODB. It's particularly tough to get dinged for ZCML when we ripped it out and made it completely optional, and we never relied on ZODB at all. Traversal is optional, of course, although often the existence of a choice is infuriating to folks. - (S)he says "Ditch Paster." You needn't use paster to create an application. It's perfectly possible to use Pyramid without paster. The first chapter of the documentation is dedicated to such a task. If you mean "make non-use of Paster the default and don't supply any application templates", meh. Obvious downsides to that. - (S)he says. "Don't depend on all of repoze".. "repoze" is a brand, not a piece of software. The only actual repoze software that Pyramid itself relies on is "repoze.lru", which is a module that does LRU caching. It's 84 lines of non-test code. The salient points (s)he has: - It's a goal to provide better "rails" in the form of defaults. This is something I've been hoping that Akhet and/or Khufu will supply, but we're still in the relatively early stages on both. - The documentation would indeed be better if we had fewer ways to do things. - 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.
