As someone who's new to web development in general and Pylons in particular, I'm trying to make sense of the Pyramid announcement. We picked Pylons without spending serious effort investigating the various alternatives because (1) seriously investigating each of the numerous Python web frameworks would have taken way too long, (2) Pylons seemed very popular (therefore easy to find support), and (3) Pylons' philosophy and design goals seemed a much better fit for what we were wanting than the other popular frameworks.
Since I'm so new to the scene, I'm having a bit of trouble following some of the discussion regarding Pyramid that takes for granted knowledge such as Pylons' architectural deficiencies, the pros and cons of Pyramid's Zope-based approach, etc. We've invested a bit in learning Pylons but haven't yet started any code. So I'm trying to figure out the best way to proceed for our project: Should we proceed with Pylons, since it isn't going away, and since a Pylons-to-Pyramid upgrade path will exist at some point? (I saw a comment that upgrading in the future will be easier if you avoid the use of Pylons pseudo-globals like tmpl_context and request to ease the Pyramid transition; since I'm very new to Pylons and the code I've seen uses those pseudo-globals heavily, what does avoiding them look like?) Should we learn BFG and start developing in that, since Pyramid is currently a rebranded BFG? (I've hardly looked at BFG, and I'm unclear from the discussion to what extent the final Pyramid release will resemble the current BFG.) Should we dive straight into Pyramid, on the assumption that it'll be production-ready by the time our app is? (From the sounds of things, it's probably still too bleeding-edge for us to want to try this.) One last question, which hopefully won't come across as flamebait, and which is probably hard to answer, since it may require a crystal ball... How stable is all of this expected to be in the long term? Our goal is a web-based application that we hope to be selling and supporting for five years or more, and it doesn't give me a good feeling to see that the framework we'd picked is announced as transitioning from 1.0 to legacy before we could even start coding. Is Pyramid expected to be stable? Or would another framework be better for extended-long-term use? Or is it silly to expect this kind of stability for web development? (Like I said, we're new to web development in general.) Sorry for contributing to the noise surrounding the Pyramid announcement. Thank you for any help. -- Josh Kelley -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
