> Anybody have ideas on how to change the settings framework not to be
> required at load time?
I'm not sure how acceptable this would be, but what springs to mind
immediately is refactoring LazySettings and Settings to push all of the
settings-loading logic into the Settings used, and using a Se
On 8/22/06, JP <[EMAIL PROTECTED]> wrote:
> I agree with basically everything in that post. Models are too tightly
> tied to their admin representation. It is too hard to use another ORM
> with django's contrib apps, and fairly pointless to use one if you
> can't do that. The admin app itself coul
I agree with basically everything in that post. Models are too tightly
tied to their admin representation. It is too hard to use another ORM
with django's contrib apps, and fairly pointless to use one if you
can't do that. The admin app itself could benefit greatly from another
rewrite, to simplif
