Adrian Holovaty wrote:
I've been wanting to make the "core" and "auth" models optional for
installation, effectively removing the "django-admin.py init" command
and requiring people to install "core" and "auth" explicitly.
I'd say I'm against it. I don't know of any stats but my feeling is that
removing them would annoy more people with explicit installation of very
common parts. These preinstalled things also help to show new users what
Django can do, not everyone read docs.
Another thing that really scares me: you create a common case of a
default Django app without an admin, hiding very great (should I say
unique?) feature and big selling point.
However, we shouldn't make it any harder to get started using Django
-- and having to install "core" and "auth" would require extra steps
that aren't currently necessary.
A single 'init' call for a framework seems reasonable necessity. And
those extra steps anyway will be needed when your app outgrows tutorial.
So a solution that Jacob and I came
up with is introducing app dependencies.
But this idea is just great! +1
Hence, instead of the tutorial saying "django-admin.py init", it would
say "django-admin.py install admin", which would automatically install
the auth app and anything else that's needed.
One more thing: general 'init' has another semantics. It's a framework
installation instead of some core app installation. So if later we'll
want to make some other initialisation things it would look more natural
under 'init' than 'init something'.
