On Jan 14, 2008 2:19 PM, "Martin v. Löwis" <martin at v.loewis.de> wrote: > > Correct. We don't need item access anymore. However the struct seq > > should still be slice-able for functions like time.mktime(). > > Can you please explain that? What application do you have in mind? Well, mktime() assumes its argument to be a tuple, and there are plenty of places that either emulate its API (like calendar.timegm()) or provide a tuple for it. I wouldn't want to lose the ability to manually construct a tuple to go into mktime() and friends. -- --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