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 with full handling of leap
> years before 1900 (correct me if I'm wrong there Chris)
I'm +1 for option (2), and -0 on option (1). Option (1) just solves
the problem a couple places, 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")
Since strftime is a public method of DateField attributes that people
can (and probably do) use (which right now are standard datetime
objects).
Cheers,
Mike
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
