[issue23084] Expose C struct timespec (nanosecond resolution) in time module

[mdcb]

mdcb added the comment:

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.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue23084>
_______________________________________