-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bad test case in TestComplexDateTimes #141
Comments
Hmm I think it's because some flag control the auto-complicated year if the
|
I was curious about that myself the other night. Did the switch to contexts or my merge for Python v3 break something? |
I don't think so. The tests are failing because the check to compare two dates is not correct. i.e. (self.mth < 12 and
self.dy < 30 and
self.hr < 23 and
self.mn < 2) always fails if say, I think it should've been something like datetime.datetime(self.yr, self.mth, self.dy, self.hr, self.mn) <= datetime.datetime(self.yr, 12, 30, 23, 2) |
please do create a pull request with what you feel it should be so we can fix this |
Well I get what you are saying for... Yes I made a stupid logic mistake here. Also be fixed in #142. |
Thanks! |
File :
TestComplexDateTimes.py
- Function :testDate3ConfusedHourAndYear
The check for
self.yr + 1
doesn't seem right. It always fails ifself.mn
> 2, irrespective of the current date.PS:- There are a couple more similar bad tests in the same function.
The text was updated successfully, but these errors were encountered: