> * ease of finishing > * lack of best practices http://code.djangoproject.com/wiki/DosAndDontsForApplicationWriters
It's up to us users to make that document more complete if there really is stuff missing. Django uses a good middle-level approach currently: it adds many basic stuff to the project and app structure, but leaves out stuff that will only be needed for bigger projects. And - for example if the models/ vs. models.py stuff goes in - will support the python way of handling it by either using direct modules or packages with submodules, depending on the needs of the programmer. I don't think that slimming that down to just one or two files will reall make things easier, neither do I think that blowing that up out of proportion would make it easier. It _is_ easy to get startet - install Django, init your database, add models, install them, use them. That's far easier than most other frameworks get, because with them you need to write at least rudimentary app code (or use half-brained scaffolding). bye, Georg
