Message126574
David,
Can you weigh in on this?
I am -1 on improving Internaldate2tuple(). I think the module should provide a function that would return an aware datetime object instead of a timetuple.
The proposed patch will make error reporting from Internaldate2tuple() inconsistent: invalid bytes result in None return while non-ASCII characters in strings would raise an encoding error. While I don't like the "if not mo: return None" logic, if compatibility with 2.x is the goal, encoding errors should be caught and converted to return None. |
|
Date |
User |
Action |
Args |
2011-01-19 23:00:48 | belopolsky | set | recipients:
+ belopolsky, r.david.murray, lavajoe |
2011-01-19 23:00:48 | belopolsky | set | messageid: <1295478048.58.0.337818535593.issue10947@psf.upfronthosting.co.za> |
2011-01-19 23:00:42 | belopolsky | link | issue10947 messages |
2011-01-19 23:00:42 | belopolsky | create | |
|