Hi :) Well, I'm pretty sure that the pylonsproject ecosystem would love to have more and more people who identifies with the ideas of the project. I mean, it doesn't need to be a 100% match, but there's have to have some.
Seriously, just because you didn't feel at home it doesn't mean you can start bashing it. On the Zope inheritance subject. Well, repoze.BFG/Pyramid is what it is due to Zope. And most people who first came to it was attracted by that fact. One can definitely say that Zope2/3 is/was a huge and ambitious project trying to cover lots of different use-cases and they have succeeded. It turns out that the components that were used to achieve that were stuck in it and not reusable at all. It was something like you have in djando today. "Want to use the django orm on a pyramid project? Just install django and use it!" That's when the "repoze" project was needed. Those guys helped build Zope. They knew exactly what parts of it was worth exposing as plain reusable python components. And they were instrumental at doing that. Zope still hides a lot of nice features that only people with who know it intimately can go there and get back with something nice for people like you use it on your projects. So, had problems reading the code? Heh :) Go read Zope code ;) Or even Django because it suffers from the same evil... Traversal. There's not much to say here about it seriously. BFG/Pyramid allows one to write from very teeny tiny web-toys to huge user-driven deep intranets. Can't think of a huge system with thousands of url-mapped code. Just can't... Traversal solves that problem nicely. ZODB is great. You probably don't know what you are talking about here or probably hasn't worked on enterprisey intranets. Otherwise you'd notice ZODB is great. ZODB+Traversal is "the" perfect match. zope.interface. It's just one more problem that Zope solved but probably don't apply to you because you have no idea how to apply it. It's a very nice way to create extensible/pluggable software by creating layers. What do you suggest for that? entry points? So, are you sure Pyramid is for you? You know, you better check because Pyramid can do all that. -Fernando On Thu, Mar 3, 2011 at 2:39 PM, Stephen Lacy <slacy+perso...@slacy.com> wrote: > Okay, chiming in here. :) Yeah, this is my post. I've been pretty quiet > here. > Sorry for the somewhat negative tone, as you can imagine, the post was > written after spending several hours digging through a very large amount of > the Pyramid source code trying to figure out the answer to what seemed to be > a very simple question. Yes, I could have asked here, or on #pylons, and > maybe I should have. But, at the same time, I think that "read and > understand the source" is an important aspect of a good framework, and > that's what I was most frustrated about. > This is also after, early in my project, spending several weeks pouring over > the "state of code" for both sessions and auth/auth. After looking at > several solutions, including repoze.who (or is it repose.who v2) beaker, > pyramid_beaker, etc. I found that there wasn't anything that really met my > needs or worked the way I wanted. I ended up writing my own auth/auth and > sessions systems for Pyramid, and amazingly, it's not that much code. I was > puzzled why there were so many seemingly complex solutions to what at it's > heart is actually some fairly straightforward code. > I'll give a look at the design defense document, but I'm afraid that from a > practical perspective, it's not really going to address some of the core > issues. > Granted, I'm coming from a Django background, and decided to explore Pyramid > because of it's database-agnostic view (I'm using MongoDB). But, I've come > to the conclusion that the plugin-centric view of the world has led to a > dependency-laden and hard to understand code base, especially for a "1.0" > product. > I'm really sorry for the negative tone of that post, like I said it was > written after a fairly large amount of frustrating code analysis, and that's > just the mood I'm in. At the end of the day, Pyramid works, it powers my > site, and has been quite stable and easy to work with... > Steve > On Thu, Mar 3, 2011 at 9:29 AM, Gael Pasgrimaud <g...@gawel.org> wrote: >> >> I suggest to rename this thread "Some trolls about Pyramid" >> >> -- >> Gael >> >> On Thu, Mar 3, 2011 at 6:54 AM, Peter Alexis <palexis2...@gmail.com> >> wrote: >> > Just happened to see a blog about Pyramid, >> > >> > >> > http://slacy.com/blog/2011/02/why-im-unhappy-with-the-pyramid-web-framework/ >> > >> > -- >> > 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. >> > > -- > 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.
