Pylons and BFG, sitting in a tree, k-i-s-s-i-n-g

First, repoze.bfg had its long-awaited 1.3 release last week.  For fans of the lightweight framework, this release was a nice wrapping-up point.  i18n/l10n and lots of little tweaks to scratch itches reported by developers.  Not only was Chris fast getting those wishes out the door, he did his usual exceptional job on getting the docs up-to-date.

As it turned out, getting 1.3 out the door was important.  It’s the last major release of BFG, which is now in maintenance mode, because…

…Pylons and repoze.bfg are merging!  First, the projects are merging.  Ben Bangert and Chris McDonough as project leads, plus the core developer teams for each project, have combined forces into the Pylons Project.  And the first deliverable is already evaluation-ready.  BFG 1.3 has been renamed Pyramid and will serve as the lightweight web framework for other activity in the Pylons Project.

Because it is based on BFG, Pyramid gains 600+ pages of docs, 100% test coverage, and many other qualities under the banner of “Small, Fast, Documented, Tested, Stable, Friendly, Extensible.”  In addition, Pyramid adds new machinery BFG to fulfill Pylons 1.x style programming.

Both repoze.bfg 1.3 and Pylons 1.x will continue a long period of bug fixing.  Applications that don’t want the change, but want maintenance, will thus be pleased.

I had a chance to meet with Ben, Mark Ramm, Chris, and Chris Rossi in Vegas a few weeks ago to talk about all of this.  It was an exceptional trip.  So often you see pride and egos in open source projects cause forking and splintering.  In this case, projects did the opposite: join forces to maximize how many resources are available for producing something of long-term quality.

Moreover, it’s fun working with new people and getting fresh ideas.  The problems that were solved 3 years ago in the last big cycle of Python web frameworks aren’t the same as the problems to solve in the next 3 years.  I honestly believe the Pylons Project will have some fresh ideas to bring to the table, as well as a commitment to meat-and-potatoes excellence in documentation, testing, support, speed, etc.

Developers from different communities (Pylons, Zope, etc.) have a new choice, one with momentum, very long experience in writing and supporting large applications, and a good group of people involved.  I’m looking forward to the next 3 years.


4 Responses to “Pylons and BFG, sitting in a tree, k-i-s-s-i-n-g”

  1. Calvin Hendryx-Parker Says:

    I’m very excited about the merging of the projects and the momentum that will be created. BFG appears to have been gathering steam, but now that you have the Pylons community behind it as Pyramid, anyone hesitating to use it has no reason to wait now.

  2. Chris Shenton Says:

    I’m really glad to see this: instead of developers having to chose either/or, they can have both. The confidence the merge gives to long-term development is a big win.

    Thanks guys!

  3. Tom Lazar Says:

    And to think, just two weeks ago i told people at the Plone Conference that the only reason *not* to use Pylons (as a light-weight alternative to Plone) was the existence of BFG 🙂

    Needless to say, I’m excited, too and looking forward to the next three(?) years!

  4. Matt Hamilton Says:

    This is great news. 🙂 Anything that merges some of the python web frameworks is a big +1 in my book. Also to have the combined knowledge and battle scars of Zope veterans adopted on a wider scale and incorporated into wider projects is a bonus.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: