When Django Fails? (A response)
lazypython.blogspot.com
lazypython.blogspot.com
> The biggest issue I have is that model syncing fails
> silently (it's as if the app doesn't exist) if an
> import in the app models file dies with an exception
> (for instance, not found).
I've wasted hours trying to figure out those kinds of silent failures... it's not much fun. Another one that stopped me in my tracks for about an hour is that an app must have a models.py file to run unit tests, even if your application doesn't have any models. If it's not there, instead of just saying 'models.py not found' it says something like 'application <your app name> could not be found'. As others have said though, I guess that's the price you pay for the luxury of having a framework to do the low-level dirty work for you.
Nobody is saying "[Django|Rails] fails as a tool/project/framework", the topic here (and in the related submission about Rails) is how do the tools we use respond to error, how clear is the message we are given and weather or not these responses could be clearer or friendlier. In short, "useful error messages".
I think it's an interesting and useful topic of discussion and I submitted this link to be complementary to the story about Rails (though I admit I probably should have just added it in a comment to that story), not to some how put Django against Rails (which seems to be a point of misunderstanding) or to put Django itself down (which wasn't anyone's intent).
Do you often judge articles by their titles and then proselytize to your peers?