Earlier this week, after several months of hard work and some delay, Django 1.2 was finally released. This is probably the most exciting release since Django’s debut, and brings long waited features, like multi-db support and a user “messages” framework.
Yes, I said Django 1.2 comes with built-in user “messages” framework. Great, isn’t it? Django really needed a built-in contrib app to solve this problem. This doesn’t mean, however, that Django-Flash will be discontinued or abandoned.
So, if you use Django-Flash in your projects, don’t worry! Nothing will change. Django-Flash is already compatible with Django 1.2, and we’ll keep improving Django-Flash for a number of reasons.
First of all, we care about the people who use our software. We won’t break your stuff if you decide to upgrade to a newer version of Django – or if you decide to keep using the previous version.
Also, freedom of choice is a good thing. You know, there’s not only one true way to solve every problem. People should be free to choose whatever tool they think is right in a given situation.
For example, based on my first impressions, there are a couple of things I didn’t like at all about the new user “messages” framework:
- It’s verbose even for the simple cases
- It ties messages to priority numbers, encouraging you to use it like a logging/debugging framework. I mean, a user “messages” framework is not a logging/debugging framework, right?
But that’s just my opinion. I guess this is what makes open source so great!
Posts em Português
Posts in English