Comment 9 for bug 492173
Revision history for this message
| Craig Marshall (craig9-deactivatedaccount) wrote | #9 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
f33e652
(Get the code!)
I have figured out why this is happening, when it's printing January of year 1, it looks back to december of year 0 to see if it can carry some days over, but of course there is no year 0. Fortunately the python calendar module thinks that Jan 1st year 1 was a Monday, so there is no problem with ignoring the previous year in this case.
I have written a patch, could some folks test it and see whether it works for them too? It works for me here on a Win 7 machine with revision 9791.