[egenix-users] mx.DateTime.now()accuracy

egenix at jf-gosset.com egenix at jf-gosset.com
Tue Feb 10 17:17:17 CET 2009

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? 


More information about the egenix-users mailing list