This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Alexander.Belopolsky
Recipients Alexander.Belopolsky, Alexandre.Zani, barry, belopolsky, djc, lemburg, r.david.murray
Date 2012-06-04.17:45:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAP7h-xbVbVSNPxdtYd-dxmsTjEwa6bGgqb8cxQKS6MVoUU-g3g@mail.gmail.com>
In-reply-to <1338831189.04.0.931111112346.issue14908@psf.upfronthosting.co.za>
Content
On Mon, Jun 4, 2012 at 1:33 PM, Alexandre Zani <report@bugs.python.org> wrote:
> I think the easiest and most intuitive approach is to simply define timestamp()
> as being the reverse of fromtimestamp().

I would like to invite everyone to review the discussion leading to
closing of issue 2736.   We cannot implement "the reverse of
fromtimestamp()" because fromtimestamp() is not reversible in presence
of DST and because float cannot represent all values that datetime
supports.  Both issues can be resolved, but I did not see any solution
that I would call intuitive.

Is anyone motivated enough to port mxDT's ticks() method to datetime?
I don't think we need to reinvent the wheel.
History
Date User Action Args
2012-06-04 17:45:52Alexander.Belopolskysetrecipients: + Alexander.Belopolsky, lemburg, barry, belopolsky, djc, r.david.murray, Alexandre.Zani
2012-06-04 17:45:51Alexander.Belopolskylinkissue14908 messages
2012-06-04 17:45:51Alexander.Belopolskycreate