[issue9005] Year range in timetuple

Alexander Belopolsky added the comment: Committed in r85441. -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mai

[issue9005] Year range in timetuple

Alexander Belopolsky added the comment: Mark, Do you agree that conditions mentioned in msg109329 and msg109340 are never triggered? -- ___ Python tracker ___ _

[issue9005] Year range in timetuple

Alexander Belopolsky added the comment: Similarly, it appears that if (*m < 1 || *m > 12) { --*m; normalize_pair(y, m, 12); ++*m; /* |y| can't be bigger than about

[issue9005] Year range in timetuple

Alexander Belopolsky added the comment: Reopening to consider removing a special case in days_before_year(..). After r82128, year cannot be <= 0. -- stage: committed/rejected -> commit review status: closed -> open Added file: http://bugs.python.org/file17869/issue9005c.diff

[issue9005] Year range in timetuple

Alexander Belopolsky added the comment: Committed in r82128. -- stage: commit review -> committed/rejected status: open -> closed ___ Python tracker ___ _

[issue9005] Year range in timetuple

Changes by Alexander Belopolsky : Added file: http://bugs.python.org/file17729/issue9005b.diff ___ Python tracker ___ ___ Python-bugs-list mail

[issue9005] Year range in timetuple

Alexander Belopolsky added the comment: I raised this issue on python-dev and Guido said "OK." See "[Python-Dev] Year 0 and year 10,000 in timetuple", http://mail.python.org/pipermail/python-dev/2010-June/100682.html I am attaching a "commit ready" patch which contains a few more test cases

[issue9005] Year range in timetuple

Alexander Belopolsky added the comment: Note that a recently closed issue 7150 similarly tightened up datetime operations by making out of range dates raise OverflowError rather than produce non-sensible result. This case is not a clear cut, but now with timezone.utc available in datetime mo

[issue9005] Year range in timetuple

Changes by Alexander Belopolsky : -- stage: needs patch -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubs

[issue9005] Year range in timetuple

Changes by Alexander Belopolsky : -- keywords: +patch Added file: http://bugs.python.org/file17722/issue9005.diff ___ Python tracker ___ __

[issue9005] Year range in timetuple

New submission from Alexander Belopolsky : Current datetime.timetuple() implementation goes out of its way to support edge cases that produce timetuples beyond the naive datetime range: >>> t1 = datetime.min.replace(tzinfo=timezone.max) >>> t2 = datetime.max.replace(tzinfo=timezone.min) >>> pri