I love Django, not just because it on top of Python, but more because it keeps its philosophy: All Zen of Python is respected with batteries included. The Ponies' framework has basically most tools and mechanisms a WebDev would want to have as such authentication, ORM multi-DB or template engine. But where Django becomes definitively ...

Lately, I worked on Django DBBackup, I was remaking the database command system: classes allowing launching of backup or restore commands through subprocess.Popen. There was no unit tests and major part of them are based on command line but contrary to what I though mock out Popen took me a some time.

I have long refused to use tox in my Python projects, I though to test code against multiple version Python was a task which should be made by CI tools. After contribute to several projects, I learned to appreciate it when I want to test code with different aspects. I was wrong and for me ...

Every one has already test a big sized app realizes he must write his own test framework for make clear tests with easy reading and usage. For example, Django has its own test framework, inherited from unittest, for ease tests for models, views, mails and more. Even with Django I sometimes need to create modules ...