[issue9034] datetime module should use int32_t for date/time components

2014-10-15 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: See also #17884. -- dependencies: +Try to reuse stdint.h types like int32_t ___ Python tracker ___

[issue9034] datetime module should use int32_t for date/time components

2014-06-29 Thread Alexander Belopolsky
Changes by Alexander Belopolsky : -- assignee: belopolsky -> ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: ht

[issue9034] datetime module should use int32_t for date/time components

2014-06-17 Thread Mark Lawrence
Changes by Mark Lawrence : -- versions: +Python 3.5 -Python 3.3 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue9034] datetime module should use int32_t for date/time components

2011-01-10 Thread Alexander Belopolsky
Changes by Alexander Belopolsky : -- versions: +Python 3.3 -Python 3.2 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue9034] datetime module should use int32_t for date/time components

2010-06-19 Thread Alexander Belopolsky
New submission from Alexander Belopolsky : """ As an aside, I dislike the fact that the datetime module uses a C 'int' for date ordinals, and clearly assumes that it'll be at least 32 bits. int could be as small as 16 bits on some systems (small embedded systems?). But that's another issue.