On Thu, Nov 25, 2010 at 12:34 AM, Venkatraman S <venka...@gmail.com> wrote:
> But, Pinax is a great solution when you > want to do anything > 'social' quickly. > I'm not after 'quickly' as much as 'maintainable even after you get bored and move on'. With Plone prior to 3.x, for instance, if you attempted customizations with your own content types, or even any of the 3rd party types, you were completely on your own for upgrades. APIs changed with every release, only the core content types had tested upgrade paths, and third party content type developers often gave up and quit maintaining their add-ons. Two months ago I shut down a Zope site I had been maintaining since 2001 from Zope 2.3 to 2.7 because some of that code wouldn't work with Zope 2.8 and later, and Zope 2.7 will not work with Python 2.4 and later, and Python 2.3 no longer compiles on a modern Ubuntu release. I lost all the photos I had been hosting there prior to moving to Flickr. Now I will happily pay Flickr $25 a year to take away this maintenance pain. Last year I started working on Zine. Among my patches was one that changed storage of keywords from Python pickles to JSON because pickles are dangerous (see above -- they die if code changes). Armin rejected this because there was no upgrade path from pickle to JSON storage, and he never got around to implementing a generic db upgrade solution, so I'm now marooned in a year-old copy of code while Zine has received many patches from others. Merging with trunk and upgrading my data is my headache, but I have neither time nor money to outsource. So this is the problem. I want to code special features, but want a base platform where my code won't block upgrades. Django is nice* because the base platform is reasonably stable and has a well defined extension mechanism. If there's a CMS that lives up to these principles, that would be fantastic. * Django's interdependencies also remind me of Zope in the Python 2.1 days, which is scary. I'm in love with Flask because it's so airy, and admire BFG (now Pyramid) because it's battle-tested, but neither is suited for a CMS. Kiran _______________________________________________ BangPypers mailing list BangPypers@python.org http://mail.python.org/mailman/listinfo/bangpypers
