@Dj Gilcrease: We had some issues altering settings only with
middleware -- basically what happened was when apache got hammered,
the settings object would get totally mangled with incorrect data.
I'm not an apache expert but we suspect it was because multiple
threads were modifying settings at th
>> However, that's no reason not to have a better API on top that
>> third-party tags can use -- as long as internal tags don't break.
>
> That should be entirely possible, using either an additional decorator
> for parser functions [EMAIL PROTECTED] or [EMAIL PROTECTED]($new_api=True)`,
> or
>
Apologies if this has been asked already and I have missed it in searching,
but is there any interest in taking a patch for a BitmaskField?
Given the following (albeit stupid) example to show some usages that would
be nice to have on a bitmask field. I should note in the examples below,
the names
On Fri, Dec 5, 2008 at 4:12 AM, Kyle Fox <[EMAIL PROTECTED]> wrote:
>
> Thanks again. At this point I'm considering removing the Sites &
> CurrentSiteManager from all of our apps entirely. Maybe I was overly-
> optimistic about how Sites could be used; having to write a static
> file just to get
If I am reading the code right you should be able to set all three
settings directly in your middleware. You just need to define
TEMPLATE_DIRS = [] in your settings file and make sure the other two
are not defined at all.
http://dpaste.com/hold/96109/
And as long as that middleware is set as the
Thanks again. At this point I'm considering removing the Sites &
CurrentSiteManager from all of our apps entirely. Maybe I was overly-
optimistic about how Sites could be used; having to write a static
file just to get Sites/CurrentSiteManager working properly is
basically a deal-breaker.
--~--
I realize this wont get a lot of attention right now do to work on
1.1, but I figured I would mention it now so I can get opinions before
I start any actual work on the idea
The editable keyword in model fields as an administrative feature I
feel should not be defined in the model, it is still fi
On Thu, Dec 4, 2008 at 03:34, David Cramer <[EMAIL PROTECTED]> wrote:
> When the done() method is called, the session is also cleared unless
> done(). Maybe this should only happen if say a ValidationError isn't
> raised? Maybe a setting that makes this not happen? In all of my
> situations it mak
