> Ever tried to integrate Django or Celery into a project whose configuration comes from .ini files or some other method? You end up writing your own configura

> Ever tried to integrate Django or Celery into a project whose configuration comes from .ini files or some other method? You end up writing your own configuration layer to get something that Django approves of. I'm doing exactly that in my current project. It wasn't so bad, just a couple lines in settings.py. ConfigParser FTW! > In the end, convention over configuration (just put your files in the magic locations, for example) is just another term for developer arrogance: of course my way is natural and everyone will want to think like me! I'd argue that Flask or Pyramid encourage a form of that too, just in a different place. Yes the Django devs have decided where you should put many of the things, but if someone new comes to your project already knowing Django they'll know where to look for things, whereas a Flask or Pyramid project may have its own idiosyncratic layout.