John Morton <j...@angrymonkey.net.nz> added the comment: While it's true that repr() methods cannot generally be expected to eval back into an object of the same type, the old repr behaviour of the struct_time object did effectively do so. Admittedly it was a kludge due to the time module functions originally producing a tuple before the advent of the struct_time type, but code that expected repr->eval behaviour worked up to 2.5. It's also evident that who ever changed the behaviour of time.struct_time.__repr__ intended that to sill be the case, otherwise it would have produced a string of the form <time_struct ...>
So I would describe this as a bug, otherwise you'd have to call it an undocumented behaviour change :-) The question remains, how to fix it? Should the repr output change to time.struct_time((tm_year, tm_mon, tm_mday, tm_hour, tm_min, tm_sec, tm_wday, tm_yday, tm_isdst)) or implement the keyword argument form? (Note: python3.0 shares this new behaviour) ---------- versions: +Python 3.0 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue5907> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
