Hi,
First of all, congrats to the core team for the first rc of the 1.4 release!
Some great changes have been made on the admin for this release. One of
them is the add of the "get_inline_instances" [1], that gives the
possibility to change the inlines list at runtime.
I've a little suggesti
with a patch, as you've suggested [1]. And I'll let
you be this pragmatic judge! :)
Will all my respect,
Yohan
[1] https://code.djangoproject.com/ticket/17856
On 03/08/2012 05:35 PM, Carl Meyer wrote:
Hi Yohan.
On 03/08/2012 07:04 AM, Yohan Boniface wrote:
Some great changes have
Hi,
In Django's documentation, the 2 following points are mentionned [1]:
- About date formating:
"Uses the same format as PHP's date() function (http://php.net/date) with
some custom extensions."
- About the specific "c" format:
"ISO 8601 Format." e.g. : 2008-01-02T10:30:00.0
Hi Stephen, Hi Ian, Hi all,
As you say Stephen, isoformat is handling the timezone offset for non naive
datetime, and so does Django in the "c" date formatter. And I should have
noticed and mentionned this in my previous email.
I'll take the time to give a better look to this issue, with these new
2011/6/28 Stephen Burrows
>
> The "O" formatter - or more specifically, the "Z" formatter - does
> include that bit of magic. Is there a particular reason for this?
>
I ask myself the same question. Why for the "Z" (and co) and not for the "c"
?
> Also, if a timezone is assumed, wouldn't it ma
I've created a ticket to propose a little change in the documentation :
https://code.djangoproject.com/ticket/16392
Yohan
2011/6/29 Yohan Boniface
> 2011/6/28 Stephen Burrows
>
>>
>> The "O" formatter - or more specifically, the "Z" formatter - do
