> On the other hand, I guess *just* the existance of a "timetuple()" > method is as good an indicator as any. Good point. But timetuple() is also the proposal's weakness, because you don't know in which timezone it is expressed. I think utctimetuple() would be more useful -- mxDateTime can support that, and so can datetime, when a tzinfo object is given. You could fall back on timetuple() if utctimetuple() doesn't exist. (Hm, I just found that utctimetuple() returns the same as timetuple() when the tzinfo is None -- that doesn't seem right.) --Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4