Hi all,
To complement next week's sprint at DjangoCon US in Portland,
I'd like to announce a local sprint happening in Berlin, Germany:
https://code.djangoproject.com/wiki/Sprint2011Berlin
When: Friday, September 9, 2011, 9am - 10pm
Where:
Jonas und der Wolf GbR
Manteuffelstraße 40
10997 Ber
On 01/09/11 21:46, Reinout van Rees wrote:
> Passing the view object to the template by default seems to me to be an
> absolute no-brainer. Class based views ought to mean you get the view
> object in your template, right? But Django doesn't do it. So... is there
> a specific reason for it?
Like
On 25/08/11 00:39, Russell Keith-Magee wrote:
> On principle, I have no objection to the idea of making the admin
> templates more robust in the presence of TEMPLATE_STRING_IF_INVALID;
> adding dummy values in the context sounds like a reasonable approach
> -- *if* doing this doesn't undermine bro
Hello,
The GSoC proposal "Multiple timezone support for datetime representation"
wasn't picked up in 2011 and 2010. Although I'm not a student and the summer is
over, I'd like to tackle this problem, and I would appreciate it very much if a
core developer accepted to mentor me during this work,
Hi Aymeric,
First, thanks for all your triage work on track, it's very much
appreciated. This is a large proposal, but I think it covers the issue
pretty completely.
I agree with your approach of using UTC internally and converting on output.
My main concern with your proposal is that it may req
On Sep 3, 9:19 pm, Paul McMillan wrote:
> Hi Aymeric,
>
> First, thanks for all your triage work on track, it's very much
> appreciated. This is a large proposal, but I think it covers the issue
> pretty completely.
>
> I agree with your approach of using UTC internally and converting on output.
>
Great job on summarizing the issue!
I have one concern though. Can you please explain why is USE_TZ option
better than introducing e.g. UtcDateTimeField?
USE_TZ=True will break all existing code (including external apps) which
relies on django 1.3 documented DateTimeField behavior, this can be
