On Thu, 2006-07-06 at 11:20 +0800, Russell Keith-Magee wrote:
> On 7/6/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
[...]
> One idea that was bounced around in my conversation with the
> client was
> that TIME_ZONE defaults to empty (or None, preferably) and if,
>
On 7/6/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
Wealready spend enough time helping with people with basic Apacheconfiguration; many of us would get it right, but they aren't the oneswho will be posting to the mailing lists. Do we need the extrainconvenience?
True. This is a very compellin
On Thu, 2006-07-06 at 10:11 +0800, Russell Keith-Magee wrote:
>
>
> On 7/6/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
> Anybody have thoughts about this?
>
> Thinking about it further, I am more and more inclined to go
> with option
> #2
On 7/6/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
Anybody have thoughts about this?Thinking about it further, I am more and more inclined to go with option#2: don't mess with the environment when running Django componentsembedded in another application. But I may be insane (the phrase has
ce
On Tue, 2006-07-04 at 19:08 +1000, Malcolm Tredinnick wrote:
> I was having a discussion today with a client who are using Django
> templates inside their own code, without using the ORM or views.
>
> It initially started out because they were using the old
>
> os.environ['DJANGO_SETTING
I was having a discussion today with a client who are using Django
templates inside their own code, without using the ORM or views.
It initially started out because they were using the old
os.environ['DJANGO_SETTINGS_MODULE'] = '__main__'
hack and had discovered that the timezone was be
