nuclearpanda.com

Django method rename without documentation update just ate hours of my life

I’m a Rails guy, but I’m not married to the framework. I honestly believe that no one should isolate themselves from the greater community, because one misses great learning opportunities.

So I’ve been learning Django. My goal is to put together the most comprehensive breakdown of Rails vs. Django, not to start a flame war, rather, to really inspect each framework so that each can benefit from innovations in the other.

I was working on some forms (one of my biggest complaints about Django is that everything is so explicit - ‘convention over configuration’ isn’t exactly the highest priority in the framework. This can be both a plus and a minus) - following this guide: http://www.djangoproject.com/documentation/0.96/newforms/

Apparently, clean_data has been renamed to cleaned_data. Yikes! This isn’t a new change, either (http://eggdrop.ch/blog/2007/02/15/django-dynamicforms/). This has been around since February.

Say what you will about the Rails community, at least renamed functions give a deprecation warning. Since the Django development server provides no logging information in its output, this wouldn’t apply. This isn’t going to discourage me from learning Django, but I am certainly going to note it in my list of evidence that the framework is far from mature.

 Edit: I just saw that I’m not the only one who saw this. This was apparently in the little popup notes.