I can wait for the magic removal branch.
regards
Ian
On 12/22/05, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
>
> Hey Ian --
>
> I think the best way to do this is with the event framework that's
> being introduced in the magic-removal branch. The Template can send
> an event with its Context
Hey Ian --
I think the best way to do this is with the event framework that's
being introduced in the magic-removal branch. The Template can send
an event with its Context at render time, and interested plugins can
listen to that event and modify the Context appropriately.
How does that
#925 - [patch] Refactor functionality of DjangoContext into
'processors' which can be replaced or added to
#959 - [patch]Template improvements
while I was trying to implement a 'user preferences' system
(http://feh.holsman.net/articles/2005/12/21/user-preferences) to allow
users (and anonymous
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
