On Apr 8, 10:46 am, Mike Axiak <[EMAIL PROTECTED]> wrote:
> but if Django were to "support" pre-1900
> dates, then it stands to reason code wouldn't break if written like
> this::
>
> instance.field.strftime("%Y-%m-%d")
Actually, I've backpedalled a bit in my new patch (uploaded just now).
No
On Mar 19, 10:07 pm, Philippe Raoult <[EMAIL PROTECTED]>
wrote:
> Hi everyone,
> [...]
> Anyway, the issue is that we have two different strategies for fixing
> #1443(and two different patches):
> 1. simply replace strtfime calls with custom format prints
> 2. replace datetime by a specific module
Is there any movement on this issue? I'm working on designing a site
dealing with historical data and pretty much all of the dates involved
are before 1900 (1600-1800). Would be really nice to get a solid
solution on this.
On Mar 19, 10:45 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> On
