Friday, April 1, 2011

Announcing Garbaginator!

While working on Packaginator at the PyCon 2011 sprints we discovered some serious issues in the way that Django handles garbage collection. After a huge amount of work, we managed to isolate and fix the problem. This 'fix', as it were, was only possible by doing a very sophisticated 'hack' of critical internal components of the Django Web Application framework. We also discovered that similar issues occurred in other existing Python application frameworks such as Pyramid, Flask,, Web2Py, Grok, Twisted, Tornado, Google App Engine, and Rails.

Since then the Packaginator community has been fiercely debating what we should do with our newly created set of hacks. After a lot of arguments going both ways we've decided to come up with our own application framework and release it to the world under the GPL license.

This brand new application framework ignores the lessons learned from all the other Python frameworks and embraces the cutting edge concept of Not-Invented-Here. It focuses less on features and enhancements over existing systems and much, much more on the critical concept of formal Garbage handling.

Some of the critical modules include:
  • RubberGloves (for handling dirty objects)
  • Django-Garbaginator
  • Flask-Recycling
  • Pyramid-Garbaginator
  • Garbaginator Bridgerator ('cause people always get Web2Py and confused with each other so we bridged them together)
  • BlueBream
Check out the home page at:
Fork Garbaginator on GitHub:

Note: This was an April Fool's Day Joke


    Paolo Corti said...

    1th of April :)

    Josh said...

    Keep forgetting that April Fools isn't over everywhere in the world yet. Had me for a minute there =P

    Anonymous said...

    Hi Dan,

    Can you provide more detail about the performance problem with garbage collection in Django software and other Python-based Web frameworks? Could the same problems occur in PHP-based frameworks such as WordPress, Drupal, and Joomla?