Message232930
naively and coming from C, you have time_t to represent time so even though underneath it's typedef, it gives the casual user like me comfort (2038 not accounted). I don't know the details why struct timespec was chosen rather than nanoseconds as integer, and in fact would rather leave that worry to others.
maybe a typdef PyTimeStamp would make the defacto you mention more obvious, and maybe class timestamp(int):pass in python that seems to bring even more meaning but I don't know how you map that in the C API.
more practically speaking: you're welcomed to close this issue since it's seeminly going nowhere. |
|
Date |
User |
Action |
Args |
2014-12-19 05:59:49 | mdcb808@gmail.com | set | recipients:
+ mdcb808@gmail.com, lemburg, belopolsky, vstinner, Arfrever, ethan.furman |
2014-12-19 05:59:49 | mdcb808@gmail.com | set | messageid: <1418968789.86.0.432679694872.issue23084@psf.upfronthosting.co.za> |
2014-12-19 05:59:49 | mdcb808@gmail.com | link | issue23084 messages |
2014-12-19 05:59:49 | mdcb808@gmail.com | create | |
|