> I have no desire to compete with the mxDateTime implementation. I want to
> look at some of the solutions out there and take the best from everyone and
> provide a module that will suit 95-100% of the people. For several reasons,
> which I tried to point out in my mails, mxDateTime or Zope's Datetime in
> its current states is not suitable.
That's a strange conclusion since both of these modules have been
around for quite some time (mxDateTime was started in Dec. 1997)
and obviously *are* quite suitable for a large share of Python's
users :-)
BTW, mxDateTime can do quite a bit in terms of i18n:
>>> from mx.DateTime import *
>>> DateTimeFrom('11. Februar 2002')
<DateTime object for '2002-02-11 00:00:00.00' at 816cc48>
>>> DateTimeFrom('February, 11 2002')
<DateTime object for '2002-02-11 00:00:00.00' at 81307c8>
>>> from mx.DateTime import Locale
>>> Locale.French.str(now())
'lundi 11 f\xe9vrier 2002 19:07:12'
>>> Locale.Spanish.str(now())
'lunes 11 febrero 2002 19:07:19'
>>> Locale.German.str(now())
'Montag 11 Februar 2002 19:07:25'
(hmm, I ought to insert some extra interpunctation...)
Nevermind,
--
Marc-Andre Lemburg
CEO eGenix.com Software GmbH
______________________________________________________________________
Company & Consulting: http://www.egenix.com/
Python Software: http://www.egenix.com/files/python/
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4