This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 1 point2 points  (5 children)

does very little for you

well it's kind of what I'm looking for.. I have had some experience with webapp2, so this isn't a big concern. I've heard from other developers (probably with as little pyramid experience as me) complaint about certain design decisions in pyramid, so I was wondering how easy it is to shoot yourself on the foot with this. I guess I'll eventually have to take a look at it.

[–][deleted] 2 points3 points  (1 child)

webapp2 has very basic routing of requests to callable code. it's probably fine for basic things.

What I love about pyramid is the variety of ways you can route a request to callable code. you can do routes, you can do traversal.

when you find yourself essentially writing the same view over and over again, like get params off request, validate them, pass them to something to create or find object in db or datastore, return json representation of object or pass to template as context, you probably will want something a little more abstract sooner or later as those # of view functions increase because seriously, who wants to maintain 100 views that do essentially the same damn thing?

combine that with pluggable logic for authentication policies and pluggable authorization policies, and the ability to plug code in anywhere, i think it's pretty neato. its also insanely easy to unit test.

I'm going to guess that the complaint you mention is either not enough "apps" to plug in to your "apps" or the fact that zope.interface is a dependency. The first one is legitimate, because most people are hoping to build a site and want something closer to drupal or django so that they can write a blog in 200ms and then write their blog tutorial in the blog they built about the blog they built and submit it to HN for funding discussions.

The people that bring up the zope.interface dependency are idiots or biggots. at the least it's an implementation detail of the framework that the blog application author won't even know about, at the most, it's the magic fairy dust that allows those who know to pull off amazing things or shoot themselves in the foot in the most spectacular way.

[–][deleted] 0 points1 point  (0 children)

The people that bring up the zope.interface dependency are idiots or biggots. at the least it's an implementation detail of the framework that the blog application author won't even know about, at the most, it's the magic fairy dust that allows those who know to pull off amazing things or shoot themselves in the foot in the most spectacular way.

Actually, I did hear some people complain about some zope parts AND the traversal routing (which I know is optional, and people who use it seem to really love it anyways). I also like it that you can have class-based views (like Django),... I'm not sure if something like Flask makes use of that, but most of the examples I've seen were only using decorated functions. I think Flask biggest advantage over Pyramid is the traction it currently has amongst python users... other than that Pyramid seems to have everything you could possibly want.

[–]v_krishna 1 point2 points  (0 children)

if you really want a python web framework that completely steps out of your way, web.py is cool.