Django's Class Based Views

A guest post by Garry Polley, a Python developer devoted to creating remarkable apps for the healthcare industry, and the creator of an online mathematics curriculum called GeckoMathematics. Education is a thriving passion for Garry and it's what he would do if he were not a developer.



In the Django community there has been a long running dispute since version 1.3 around class based views. I plan to give some insight into how you should use class based views. This is not an article aimed at function based views vs class based views.

Getting started with Python

In the most recent issue of the Bulletin of the American Meteorological Society (BAMS), Johnny Lin (Python guru with a very useful ) wrote a great explaining why Python is the 'new wave' in earth sciences computing. It would be fair to say that this is a widely held view, particularly considering that the AMS has hosted an annual Python symposium for the last 3 years running. While nice features like the elegant syntax and open-source nature of Python have certainly contributed to its popularity, the main reason why Johnny Lin and others are so bullish about Python is the fact that you can do pretty much everything with it.



Consider this hypothetical workflow, typical of the weather/climate sciences: