Re: mx.DateTime.now()accuracy
"M.-A. Lemburg" <[email protected]>
| Newsgroups | gmane.comp.python.egenix.user |
|---|---|
| Organization | eGenix.com Software GmbH |
| Message-ID | <[email protected]> |
On 2009-02-10 17:17, [email protected] wrote: > With the old 2.0.3 version of mx.DateTime, now() returned fraction of seconds so we had 1/100sec accuracy. > With 3.1.2 version, now() now [!] returns whole integer numbers. > > Tested with same version of Python (2.5.4). Just switched mx... package in site-packages > > Is it by design or is it a bug? On which platform are you seeing this problem ? mxDateTime does return fractions on Linux: >>> from mx.DateTime import now >>> now() <mx.DateTime.DateTime object for '2009-02-10 17:26:11.86' at 2b13fe0e78c8> -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Feb 10 2009) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try our new mxODBC.Connect Python Database Interface for free ! :::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ _______________________________________________________________________ eGenix.com User Mailing List http://www.egenix.com/ https://www.egenix.com/mailman/listinfo/egenix-users