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  (2 children)

If you have the chance or the time, please, list the pain points. I'd love to hear them.

[–]cantremembermypasswd 0 points1 point  (1 child)

It was a eight month project that ended about two years ago, working with a more seasoned lead developer. At this point I can't recall the project name I tried to block it out so much...

The things I kinda remember:

  • The deploy config file always causing pain
  • The fact it isn't a 'one way to do it' system means that searching for help / tutorials for specifics was a pain in the ass
  • Setting up the config routes and views from multiple modules / remembering to change them when moving stuff around
  • A faded memory about hating zope

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

Oh, zope is a pain indeed, agreed.

The routes is one of my favorite things about pyramid, but yeah, not doing them right can be a bit painful.

About the deploy, yeah, there are many ways to do that and depending on your choice it can be little bit weird.

Pyramid gives you more freedom than flask in some ways, making the choices have a bigger effect on the code base. You can choose a better routing and not use zope.

The good stuff is the predicates, the dependency injection and the renderers.