Pylons vs Turbogears

Question

I am considering whether I should use Turbogears or Pylons for my project. I know Turbogears2 is based on Pylons. What does Turbogears offer that Pylon does not? Thanks.

Answer 1

Turbogears emphasizes integration, while Pylons emphasizes modularity - with TG2 you get components like genshi , toscawidgets and sqlalchemy , all integrated and coordinated. Of course, you could integrate and coordinate each of them (or other template systems, widget systems, ORM, etc.) with Pylons, but, undoubtedly, many people would prefer to receive the full package (and the peace of mind that comes from knowledge has been tested in this particular version and configuration) instead of getting each part separately and doing its own integration.

Answer 2

Some time ago I came up with this on the IRC:

Imagine that you have a puzzle, and the picture in the box is a boat on the sea (yes, one of these solid ones).

With Pylons, you will begin to look at all these blue pieces and put them together, sometimes ruining, because you do not know if they are the sky or the sea.

With TurboGears, all of the blue ones are already done, and you just go and work on the ship. But if you are interested in making part of the blue, you go and cancel this part of the puzzle and build it again *.

* here the analogy breaks down a bit, because the replacement component does not need to be built from the same set of pieces :)

Answer 3

neil balkey-milner has a valuable analysis / comparison of tg and django pylons.