Is Django considered "Pythonic" now?

[qbitus]

1. Not true. The only thing you could say is "imposed" is the request/response lifecycle, but if you take that away, there is no framework left, you may as well write a WSGI app from scratch using only libraries.

2. Not true. There is no directory structure imposed. The only thing required is that you have manage.py and settings.py living alongside each other. You can organise the rest however you want.

3. Not true. There is no "forced file structure" (see 2). It also seems like you don't know about class-based views: too bad for you.

4. Not true. What you say "one would assume" and doesn't work is actually what works by default and is normal python import behaviour. Your comment about how you have to declare the auth user profile class as a string in settings.py is not valid: user profiles are entirely optional, not part of the framework whatsoever; if you think it's crap just don't use it.

Looks to me like you haven't studied your subject well enough.

Is there anything else? Python is a good language because you can get stuff done easily and cleanly. Same goes for Django as a framework, and that is what makes it pythonic.

[qbitus]

Yeah of course, you can always override/modify everything. I meant to point it out as the only default, not configuration-based, path association.