Author mdcb808@gmail.com
Recipients belopolsky, ethan.furman, lemburg, mdcb808@gmail.com, vstinner
Date 2014-12-18.23:52:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1418946735.5.0.433892883324.issue23084@psf.upfronthosting.co.za>
In-reply-to
Content
I'm going to be my own devil's advocate:

PyLong_FromLong

...

Thanks for all the links, I hadn't realized there was so much background to the issue, there is some good reading there too.
you've changed the title now, but in fact the intention was the other aspect, core nanosecond support in python. I just happened to pick timespec because it does the job and is reasonably widespread.

reading all this, and threading lighlty, I was playing with

class timestamp(int): pass
  """measure of time expressed as a number of nanoseconds"""

but that seems to loose the type information after doing arithmetics

x=timestamp(10)
y=timestamp(20)
type(x+y) gives <int>
History
Date User Action Args
2014-12-18 23:52:15mdcb808@gmail.comsetrecipients: + mdcb808@gmail.com, lemburg, belopolsky, vstinner, ethan.furman
2014-12-18 23:52:15mdcb808@gmail.comsetmessageid: <1418946735.5.0.433892883324.issue23084@psf.upfronthosting.co.za>
2014-12-18 23:52:15mdcb808@gmail.comlinkissue23084 messages
2014-12-18 23:52:15mdcb808@gmail.comcreate