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 vstinner
Recipients belopolsky, loewis, pitrou, python-dev, tim.peters, vstinner
Date 2015-03-30.01:38:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1427679497.21.0.646203929755.issue22117@psf.upfronthosting.co.za>
In-reply-to
Content
I rewrite the implementation of this issue 2 or 3 times. At the end, I decided to rewrite it again with a more incremental approach: add the new API, use the new API, and then drop slowly the old API.

I was used to rewrite the implementation multiple times to fix issues in the API and enhance the implementation. The new API now handles better rounding with more unit tests.

The datetime module only uses the new API for the datetime.datetime() constructor. It's not used for datetime.datetime.fromtimestamp(), because _PyTime_t is limited to a range of [-292 years; 292 years]. The datetime module supports a much large range: year in range [1; 9999]. So some parts of the old API will survive for the datetime module.
History
Date User Action Args
2015-03-30 01:38:17vstinnersetrecipients: + vstinner, tim.peters, loewis, belopolsky, pitrou, python-dev
2015-03-30 01:38:17vstinnersetmessageid: <1427679497.21.0.646203929755.issue22117@psf.upfronthosting.co.za>
2015-03-30 01:38:17vstinnerlinkissue22117 messages
2015-03-30 01:38:16vstinnercreate