#1443: [patch] no support for dates before 1900
----------------------------------+-----------------------------------------
Reporter: akaihola | Owner: nobody
Status: reopened | Component: Core framework
Version: SVN | Resolution:
Keywords: date 1900 datetime | Stage: Accepted
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
----------------------------------+-----------------------------------------
Comment (by Fredrik Lundh <[EMAIL PROTECTED]>):
The #3306 approach is more of a hack, though; it just fakes its way around
the C time limitations, in order to support 1900-9999. But that doesn't
help; I have dates between 1500 and 1900 in my databases... :-/
No time to dig deeper into this right now, but I'm now convinced that
putting Dalke's code in a support library, and making sure to use that
whenever the Django core converts dates, is the right solution.
Introducing a Django-specific datetime type/module may be elegant, but
it's also rather fragile if you have a view that gets data from non-Django
sources, and want to render it through Django.
I can check the license with Andrew and adapt Chris' patch, if there's
support for that approach.
--
Ticket URL: <http://code.djangoproject.com/ticket/1443#comment:10>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
