[docs] datetime.now() bug

[Sandro Tosi]

Hello,

On 2011-06-10, maquema/Martin Maqueira (SPAIN System Administrator)
<maquema at coscoiberia.com> wrote:
> I write you because I found a bug in datetime.now(). (tested in Python 2.6.6
> -r266:84297, Aug 24 2010, 18:46:32-win32) This bug is that sometime doesn´t
> return milliseconds.

Please note this is not a general bug reporting mailing-list, but it's
targetted at documentation. If you think it's a bug, you can report it
as an issue at [1] or ask for guidance on a general-purpose ml such as
python-list[2]

[1] http://bugs.python.org
[2] http://mail.python.org/mailman/listinfo/python-list

As a side note, I don't find any clear statement in the documentation
that the milliseconds should be there, while it's quite clear that the
precision is depending on the underlying (as in the operating system
ones) functions.

Cheers,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi