On 1/9/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> On 1/8/06, Joseph Kocherhans <[EMAIL PROTECTED]> wrote:
> > Here's a status update on moving dango.contib.core/auth into django.contirb:
> >>
> > * Remove Package model (and dependencies on it)
> > Ian Holsman still uses this. I'm things we
On 1/8/06, Joseph Kocherhans <[EMAIL PROTECTED]> wrote:
> Here's a status update on moving dango.contib.core/auth into django.contirb:
>
> * Move sessions from core to django.contrib.sessions (and change dependencies)
> Done.
>
> * Move sites from core to django.contrib.sites (and change dependenc
Here's a status update on moving dango.contib.core/auth into django.contirb:
* Move sessions from core to django.contrib.sessions (and change dependencies)
Done.
* Move sites from core to django.contrib.sites (and change dependencies)
Done.
* Move auth to django.contrib.admin (and change depend
Ian Holsman пишет:
> Hi.
> I'm using packages.
> I think it is a good place to put stuff like package-specific preferences.
>
> ie.. the preference of the text markup you would like
> (bbcode/markup/textile) is stored against the 'text' package.
>
> if you like delicious/furl/digg is stored ag
On 1/6/06, Joseph Kocherhans <[EMAIL PROTECTED]> wrote:
> > * Move auth to django.contrib.admin (and change dependencies)
>
> Did you mean move auth to django.contrib.auth here? Or do you really
> want it moved into admin?
My mistake -- I meant django.contrib.auth.
Adrian
--
Adrian Holovaty
hol
On 1/6/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> * Move auth to django.contrib.admin (and change dependencies)
Did you mean move auth to django.contrib.auth here? Or do you really
want it moved into admin?
Joseph
On 1/6/06, Ian Holsman <[EMAIL PROTECTED]> wrote:
>
> Hi.
> I'm using packages.
> I think it is a good place to put stuff like package-specific preferences.
I'm going to leave them as is for now. There's actually quite a bit
that depends on them that I need to take a closer look at. I'm
starting
Hi.
I'm using packages.
I think it is a good place to put stuff like package-specific preferences.
ie.. the preference of the text markup you would like
(bbcode/markup/textile) is stored against the 'text' package.
if you like delicious/furl/digg is stored against the 'bookmark' package.
FWIW
On 1/6/06, Joseph Kocherhans <[EMAIL PROTECTED]> wrote:
> Should sites be installed by init? I think it's used rarely enough
> that it shouldn't.
It's used by various bits and pieces, such as the RSS and redirect
frameworks, that need to know the fully-qualified domain name for an
object. Maybe t
On 1/6/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> > If no one is using packages I'll just drop it.
>
> This is a bit easier said than done...The content-types table depends
> on it. How about splitting this patch into several stages --
>
> * Move sessions from core to django.contrib.sessio
On 1/6/06, Joseph Kocherhans <[EMAIL PROTECTED]> wrote:
> Now that I think about it a little more I agree that core should be split
> into:
>
> django.contrib.sessions
> django.contrib.sites
Sounds good.
> If no one is using packages I'll just drop it.
This is a bit easier said than done...The
On 1/6/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> 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
On 1/6/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> 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 (insta
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
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.
Create 2 new apps, djan
15 matches
Mail list logo
