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 chris.jerdonek
Recipients belopolsky, brett.cannon, chris.jerdonek, ezio.melotti, pitrou
Date 2012-09-16.02:42:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1347763327.68.0.82607982807.issue15933@psf.upfronthosting.co.za>
In-reply-to
Content
> That won't always work for case 1 (when theclass is e.g. 'date') and for case 4 (even if it's unlikely).

Can you explain what you mean by this?  It seems the timedelta allowance would be equally valid and serve the same purpose no matter what case or whether dealing with dates or datetimes (e.g. different date objects because of (1) would also fail the `< timedelta(seconds=0.5)` check).  For example--

>>> from datetime import date, timedelta
>>> d1 = date(2012, 1, 1)
>>> d2 = date(2012, 1, 2)
>>> abs(d2 - d1) < timedelta(seconds=0.5)
False

Basically, the check is to confirm that today and todayagain are within 0.1 seconds of each other -- no matter which case.
History
Date User Action Args
2012-09-16 02:42:07chris.jerdoneksetrecipients: + chris.jerdonek, brett.cannon, belopolsky, pitrou, ezio.melotti
2012-09-16 02:42:07chris.jerdoneksetmessageid: <1347763327.68.0.82607982807.issue15933@psf.upfronthosting.co.za>
2012-09-16 02:42:06chris.jerdoneklinkissue15933 messages
2012-09-16 02:42:06chris.jerdonekcreate