➜

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 musically_ut
Recipients musically_ut, serhiy.storchaka
Date 2017-06-30.23:47:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1498866468.86.0.743233238239.issue30822@psf.upfronthosting.co.za>
In-reply-to
Content 
While investigating http://bugs.python.org/issue30302 it was discovered that the Python implementation of the datetime module was not being tested correctly.

The datetimetester.py was supposed to execute tests twice, once for the _Fast implementation (i.e. C extension code in _datetimemodule.c) and once for the _Pure implementation (i.e the Python code).

The fix is contained in the following two commits:

 - https://github.com/python/cpython/pull/1493/commits/08e7548f56838fca43b488cefe51de4bdd600f3d
 - https://github.com/python/cpython/pull/1493/commits/94d5a4e4d33a1d14a2bb1be8fbff5e1e4cd2b7a6

The bug does not effect Python 2.7 as the C version of the datetime module had not been introduced back then. However, as fas as I can tell, the fix needs to be applied to all Python 3.x branches.
History
Date User Action Args
2017-06-30 23:47:48musically_utsetrecipients: + musically_ut, serhiy.storchaka
2017-06-30 23:47:48musically_utsetmessageid: <1498866468.86.0.743233238239.issue30822@psf.upfronthosting.co.za>
2017-06-30 23:47:48musically_utlinkissue30822 messages
2017-06-30 23:47:48musically_utcreate