pep proposal : A date object for the standard library

Robin Becker robin at
Fri Dec 7 19:47:37 CET 2001

In article <3C110867.5263E6E6 at>, Chris Barker
<chrishbarker at> writes
>Are there other technical issues with mxDateTime that make it unsuitable
>for the standard lib?
the only problem with mx datetime is that the individual objects require
quite a lot of storage. Last time I heard it was 32 bytes, but I'm not
sure whether that is over and above what python needs for an object or
includes it. 

Some business time series have thousands of entries and for intra day
stuff there is no obvious frequency which would allow a convenient
sparse representation of the times. Is storage an issue? Certainly time
series analysis nerds think so, but if it's only a factor of 4 I guess
it won't matter to pythoneers.
Robin Becker

More information about the Python-list mailing list