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 bannerts
Recipients bannerts
Date 2012-02-18.09:00:49
SpamBayes Score 6.0123266e-06
Marked as misclassified No
Message-id <1329555650.42.0.80388367005.issue14048@psf.upfronthosting.co.za>
In-reply-to
Content
Note: this is my first time to submit a bug or use this system

I might have found an issue with the calendar related to the point of time in history when the date was necessary to correct by 11 days.  Anyhow, the correction is made in a GNU+linux machine, so it seems like something worth fixing in python.  

How I discovered it:
I was reading through some posts on reddit when I came up on this one:
http://www.reddit.com/r/linux/comments/9jl2t/1_open_a_linux_terminal_2_enter_cal_9_1752_3_shit/
which seemed to state that in the September of 1752, they decided to skip from Wednesday the 2nd to Thursday the 14th.  Out of curiosity, I decided to see if Python had it recorded this way by typing in the following commands in python:

>>> import calendar
>>> calendar.TextCalendar().pryear(1752)

It was not corrected for the two versions of python I tried using (2.7 and 3.2).
History
Date User Action Args
2012-02-18 09:00:50bannertssetrecipients: + bannerts
2012-02-18 09:00:50bannertssetmessageid: <1329555650.42.0.80388367005.issue14048@psf.upfronthosting.co.za>
2012-02-18 09:00:49bannertslinkissue14048 messages
2012-02-18 09:00:49bannertscreate