I would say the above is a pretty good description. I will just chime in with my experience. So I have been hacking with Pyramid for the last two years or so, one of which as been spent mostly on a single web app. The web app I'm working on has some pretty specific constraints, and at the end of the day I want to be able to control the full stack down to the last tiny detail, so I can provide the best user experience. Pyramid is ideal for this kind of situation, b/c it's so easy to swap any part of the stack in and out. For example, I had a month stint where I was experimenting with using the same templates on the front/backend. I was able to switch out my template rendering engine with very little work to accomplish this. A month later when I decided it wasn't a good fit for me, I simply switched it back. All the while I was able to keep the rest of my code intact. I would say Pyramid isn't unique in this specific example(b/c you can do the same in other frameworks), but it accurately describes the general idea behind the framework, that every part of the framework should be easily interchangeable. Key word being "easily." B/c I'm a strong believer that every non-trivial web app reaches a point where it outgrows the framework, and you'll have to start reverse engineering parts of the framework to do what you want. With pyramid you generally don't have to do any reverse engineering, b/c it leaves all of the big design details to you.
So that's kind of a long winded way of saying that Pyramid is for applications with very specific needs. On Fri, Mar 29, 2013 at 11:51 AM, Krishnakant Mane <[email protected]> wrote: > Hello paul. > > I think Piramid is a framework for complex web applications (easy ones are > easily done using DJango ). > It can also be used to just develop a web front end for an already > existing service based on xmlrpc or soap. > The stacked approach is what I personally feel makes it stand out from the > rest, although I guess turbogears does the same. > Happy hacking. > Krishnakant. > > > On 03/29/2013 10:16 PM, Paul Everitt wrote: > >> The discussion about docs turned into a discussion about Pyramid and >> target markets. Which was perfect, as Blaise and I are in some chats about >> related topics. >> >> Rather than hijack that thread, I thought I'd start a new one. What is >> Pyramid? And even more difficult, what isn't it? (I am a staunch believer >> in focus and having the courage and honesty to say "that's not us, you're >> better served elsewhere.") >> >> I'd like to listen to more ideas from insiders and casual developers >> about: >> >> - Who Pyramid appeals to >> >> - What differentiates it (in a no-bullshit, honest-to-goodness way) >> >> - What is an unmet need in the Python web frameworks space that Pyramid >> does a good job of itch-scratching for >> >> --Paul >> >> > -- > You received this message because you are subscribed to the Google Groups > "pylons-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to > pylons-discuss+unsubscribe@**googlegroups.com<pylons-discuss%[email protected]> > . > To post to this group, send email to > pylons-discuss@googlegroups.**com<[email protected]> > . > Visit this group at > http://groups.google.com/**group/pylons-discuss?hl=en<http://groups.google.com/group/pylons-discuss?hl=en> > . > For more options, visit > https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> > . > > > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pylons-discuss?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
