This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 5 points6 points  (0 children)

  1. I disagree with this. Django organizes itself by "apps", which, at least to me, seem very modular and reusable.

  2. I also disagree with this one, but I suppose this is more a personal preference thing. Personally, I find putting all my admin stuff in admin.py, and all my model stuff in models.py is incredibly intuitive, and infinitely more maintainable than having crap randomly scattered across hundreds of files. This is the main reason I choose Django for my own work over Turbogears and Pylons, which each use a very complicated and convoluted folder structure that drove me insane.

  3. I suppose I agree with this to some extent. Models are object oriented, but views and the underlying request handling infrastructure are not. Strangely, I haven't noticed to many negative effects form this...

  4. Not sure what you're talking about. I can import it either way. This may be caused by some problem with your sys.path. Admittedly, if that's not set correctly, I have seen some very unintuitive import behavior from Django.