➜

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 belopolsky
Recipients Mariatta, belopolsky, doerwalter, golly, matrixise, rhettinger, serhiy.storchaka, xiang.zhang
Date 2016-10-22.22:22:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1477174966.19.0.924369457789.issue28281@psf.upfronthosting.co.za>
In-reply-to
Content 
The patch should include an update to documentation.

1. We should probably explain that python -mcalendar does not reproduce the output of UNIX cal.  For example, on Mac OS (and various Linux variants): 

$ cal 9 1752
   September 1752
Su Mo Tu We Th Fr Sa
       1  2 14 15 16
17 18 19 20 21 22 23
24 25 26 27 28 29 30


but 

$ python3 -mcalendar 1752 9
   September 1752
Mo Tu We Th Fr Sa Su
             1  2  3
 4  5  6  7  8  9 10
11 12 13 14 15 16 17
18 19 20 21 22 23 24
25 26 27 28 29 30

2. We should explain that while the calendar module relies on datetime, it implements an infinite calendar with a period of 400 years.

3. A reference should be made to ISO 8601 for our treatment of nonpositive years.

Given ISO 8601 and the simplicity of this change, I don't think Raymond will insist that we continue imposing datetime-like limits, but I would like to give him a chance to renew his objection once the no-limits calendar is documented.
History
Date User Action Args
2016-10-22 22:22:46belopolskysetrecipients: + belopolsky, doerwalter, rhettinger, serhiy.storchaka, matrixise, xiang.zhang, Mariatta, golly
2016-10-22 22:22:46belopolskysetmessageid: <1477174966.19.0.924369457789.issue28281@psf.upfronthosting.co.za>
2016-10-22 22:22:46belopolskylinkissue28281 messages
2016-10-22 22:22:45belopolskycreate