News for hackers. Stuff that matters.

A comment on Notes from MPUG: "Python one-liners" talk. Parent comment

Re:Notes from MPUG: "Python one-liners" talk by aleyan on Monday June 03, 2013 @04:50PM (#5815923)
Doesn't quite work as expected. From "python -m calendar 1752 9" I get:

     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
"cal 9 1752" on the other hand gives:

      September 1752
   S  M Tu  W Th  F  S
         1  2 14 15 16
  17 18 19 20 21 22 23
  24 25 26 27 28 29 30
Maybe python doesn't auto recognize the timezone?

EDIT: Actually this is pretty bad because python gets all the days of the week before September 1752 in North America wrong.

[ Parent | on HN ]
Re:Notes from MPUG: "Python one-liners" talk by msluyter on Monday June 03, 2013 @05:32PM (#5816166)
Interesting calendar trivia. The Gregorian calendar was adopted in Sept. 1752:

Britain and the British Empire (including the eastern part of what is now the United States) adopted the Gregorian calendar in 1752, by which time it was necessary to correct by 11 days. Wednesday, 2 September 1752 was followed by Thursday, 14 September 1752.

So, in this case, it looks like cal is doing the right thing.

[ Parent | on HN ]
Re:Notes from MPUG: "Python one-liners" talk by dragonwriter on Monday June 03, 2013 @06:09PM (#5816389)
The python version is using proleptic Gregorian and the cal version is using the historical calendar rules for a particular locale. Which is "right" depends on what you want.
[ Parent | on HN ]