Anonymous
asked:
at what degree/in what areas of anticipated project complexity do you recommend graduating from flask to pyramid?

i guess the moment you say “man this is a pain in the ass i wish i had zope.interface”

honestly, you don’t actually need to start with flask. pyramid just has a slightly higher learning curve because it exposes more of its parts. but the sample code in the root of their docs is pretty similar to the flask example, just with a few more imports and more explicit setup

pyramid actually made a list of microframeworks that went around earlier this week too

so i think the difference is more about how much stuff you expect you’ll want to customize. not that flask makes it particularly difficult, but pyramid is pretty much built to have large chunks of functionality swapped out if you so desire. the cost is that the docs are a bit denser. if that sounds like a good tradeoff to you then by all means just use pyramid already

i think i draw the line at expecting to need more than a few endpoints, mainly because i have a better handle on how to organize pyramid than i do flask