Message49842
Logged In: YES
user_id=6380
I'm against this functionality.
It suggests an linkage between the "naive"
(timezone-unaware) time carried in the datetime object, and
the UTC space that posix timestamps represent. The entire
point of the datetime type (unless an explicit tzinfo is
passed) is that it doesn't know which timezone it represents.
When you call time.mktime(self.timetuple()), you as the
application make the determination that the timetuple (which
is still tz-unaware!) represents your current local time.
That's a fine decision for the app to make. But I don't
think users should be lured into believing there's an
equivalency inherent in the datetime type -- there isn't. |
|
Date |
User |
Action |
Args |
2007-08-23 15:47:14 | admin | link | issue1457227 messages |
2007-08-23 15:47:14 | admin | create | |
|