Should I use Pylons or Pyramid?

Question

I planned to move from Django to Pylons, but then I came across Pyramid.

What are the differences between Pylons and a Pyramid?

I read some text in PylonsBook , which currently covers Pylons 0.9.7, and wonder if I need to start for Pylons and the pyramid.

Answer 1

Pylons are not canceled, and he will continue to receive updates. However, the “future” itself is in the Pyramid. The mailing list lists Pylons 2.0. It is fully tested and better documented than Pylons 1.0, so you can jump aboard if you are fresh.

A pyramid is essentially a merger of Pylons and Repoze.bfg. Read more about this in pylons-devel .

In particular, in this opening letter. If you have deeper questions, chat on the #pylons, #pyramid, or #repoze irc (freenode) channels.

Answer 2

You want to go with the pyramid, most likely. This may seem like a more complex system, but in fact it is much cleaner and very intuitive. In addition, the documentation for the project is simply awesome and, in my opinion, even better than the django project, which is well known for its documentation.

This does not make it "like django." It is still slightly connected, and you can use any template, database, form, session management system, etc. that you like.

It is worth noting that Pyramid is the base structure, and Pylons is built on top of it.

Answer 3

If you plan to launch a new project, transfer or just study the framework, I recommend using Pyramid.

Pylons will stop its development. Meanwhile, the pyramid is a continuation of the Pylons. Thus, the code is stable. It includes most of the features from Pylons, adds new useful features.