On 1/6/06, Joseph Kocherhans <[EMAIL PROTECTED]> wrote: > Treating django.models.core and django.models.auth as special cases is > kind of confusing. They should be regular apps, but we don't want to > have to add 2 extra steps (installing the 2 apps) to get a django > project up and running. Here's a few ideas for fixing the problems.
I did a double-take on this e-mail, because it's almost exactly the same proposal as one I wrote a couple of weeks ago! :) http://groups.google.com/group/django-developers/browse_thread/thread/dc86e876af62a4cd/3413fb5e4ec2ed6c That thread died out due to discussion of the problems of a dependency system -- which seemed like reasonable pushback to me. Let's avoid the dependency thing for now. I really like your idea of "init" and "init-minimal" -- that accomplishes the clean split of auth/core into regular apps while keeping it just as easy to install the basics. Let's do it! One more idea, though, would be to split "core" into django.contrib.sessions, django.contrib.contenttypes and django.contrib.sites. Packages would go away, because they're not really necessary (we used them heavily about 1.5 years ago, but they're no longer useful). Thoughts on that? Adrian -- Adrian Holovaty holovaty.com | djangoproject.com | chicagocrime.org
