Some people have been concerned lately regarding the status of the Pylons framework in light of new effort being spent around additions to Pyramid. I thought it'd be useful to help assuage those fears, and explain a bit more about the Pylons code-base.
Pylons 1.0 was released 6 months ago, in May of 2010. Between 1.0 and 0.9.7, which were released over a year earlier in Feb. of 2009, there were almost no changes to Pylons besides deprecated bits being removed, and a few defaults changing. Most new features instead came from changes to Beaker, SQLAlchemy, WebHelpers, and occasionally Routes. Beaker, SQLAlchemy, Mako, and WebHelpers are unaffected by Pyramid: they continue to work as they have. Pyramid can use most of these packages just like the Pylons framework can. (A few webhelpers are currently incompatible with Pyramid: see pylons-devel). As these packages are also where most of the feature improvements for Pylons framework users came from, again, there's no change in that! Nothing is changing regarding the Pylons 1.x code-base from how it has been for the past year and a half. It is a mature and stable code-base that meets many people's needs. There's no reason to feel bummed or sad that it is somehow 'dead' or 'end-of-life'. It will continue to receive the same bug fixes and security fixes that it has been getting for the past 18 months, in perpetuity. Pyramid really only affects where myself and some other Pylons developers will be spending our future development efforts. As a stable and mature code-base, the Pylons framework has required a lot less of my attention lately, so my current development time spent on it has already dropped quite low. The development time I spend on the Pylons framework is not changing. With that freed up time -- and additional developers through this merger -- we can spend more effort and resources pushing ahead with Pyramid-related development. One thing we're doing is increasing our scope to tackle larger problems that were beyond the scope of the Pylons framework. The existing amount of time I've been spending on the Pylons code-base for the past 6+ months is not changing. The Pylons 1.x code-base is not changing, apps using it will continue to run. But with a larger development effort, we'll be able to build some useful additions that should help people whose needs haven't been completely met by the Pylons framework. Cheers, Ben -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-disc...@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
