I would say that Pyramid is a lot more similar to Pylons than Michael thinks.
Because of the maturity/age of the projects, a lot of the newer (and stranger) Pyramid features don't have a variation in Pylons -- but almost everything in Pylons can be quickly ported to Pyramid. The routing is *similar*. There is a package that offers some helpers to re-implement Pylons' routing in Pyramid with minimal changes -- but you're honestly better off learning the new style. Pyramid is missing a lot of the "helper" variables that were in Pylons, (like the current request, helpers, etc) Some were renamed, others were removed. You can still access them when you need them, they just need to be imported into code or populated into templates explicitly. It took me about 3 hours to migrate a medium sized e-commerce project from Pylons to Pyramid. Most of the work was just find/replace. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/d/optout.
