I'm definitely +1 on splitting out the core and auth models/tables. If
installing them is just as simple as running init and installing the
admin app is now, what's the big deal? For those who want it, it's no
harder, and you'd be able to install the admin without even realizing
you're installing
I'm -0.5 on moving the apps to the contrib area.
ok.. call me old and grizzly here, but I'm still not sold on the point.
having tables which people might not use isn't such a big deal. (it
isn't like they take up so much space, or present a risk)
ease of use is important to me. how will any of
On 12/21/05, Daniel Poelzleithner <[EMAIL PROTECTED]> wrote:
Apps sould define a __version__ in __init__.py wich sould be checked onthe dependencies check.maybe a syntax like:__dependencies__ = (('django.contrib.auth',">=0.1,!=0.2"),('my.app.bla', "==
0.3"))would require a version of contrib.auth t
Adrian Holovaty wrote:
> So how is this implemented? The simplest way we could do it is a
> __dependencies__ variable in the __init__.py of the app. For example,
> this would go in django/contrib/admin/__init__.py:
>
> __dependencies__ = ('django.contrib.auth',)
>
+1 for dependencies, but
Adrian Holovaty wrote:
> So how is this implemented? The simplest way we could do it is a
> __dependencies__ variable in the __init__.py of the app. For example,
> this would go in django/contrib/admin/__init__.py:
>
> __dependencies__ = ('django.contrib.auth',)
>
> (This assumes auth gets m
>So a solution that Jacob and I came
>up with is introducing app dependencies. The admin app, for instance,
>is dependent on auth and core. The auth app is dependent on core.
>There are many apps in Ellington (the World Online commercial CMS
>built on Django) that depend on other ones.
+1
The IN
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 t
+1000! I think it's an elegant solution to the stated problem, and
would be immensely useful on its own merits regardless. For example,
I'm using Django to write a lot of custom business logic for an
intranet, and I've already run into the dependencies issue; being
able to explicitly stat
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.
Reasoning: It's messy for the framework to create database tables that
everybody doesn't necessar
