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 ssh
Recipients demian.brecht, orsenthil, serhiy.storchaka, ssh
Date 2015-05-06.14:22:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Wouldn't int(float(expires) * 1e6) set the date much further in the future? I'm not sure why you'd do that unless the plan is to change the internal time unit to microseconds (which seems like a much bigger change, and overkill for handling this special case). Cookie strings operate at the second granularity, so I'm not sure if the sub-second precision is required.

I took a quick look at curl's code and test cases, and they use a time_t structure which doesn't have subsecond precision. Fractional time is not a part of their test cases.

Wget also appears to do something similar:
Date User Action Args
2015-05-06 14:22:27sshsetrecipients: + ssh, orsenthil, serhiy.storchaka, demian.brecht
2015-05-06 14:22:27sshsetmessageid: <>
2015-05-06 14:22:27sshlinkissue23888 messages
2015-05-06 14:22:26sshcreate