A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2002-October/029626.html below:

[Python-Dev] float atime/mtime/ctime - a bad idea?

[Python-Dev] float atime/mtime/ctime - a bad idea? [Python-Dev] float atime/mtime/ctime - a bad idea?Guido van Rossum guido@python.org
Wed, 16 Oct 2002 10:41:40 -0400
> > I wonder if we could let the tuple-ish interface return ints forever
> > (or until it's no longer supported).
> 
> That would not be easy to implement. The structseq type does not
> support unnamed sequence members (yet), which we'ld need: the int
> members would have only indices, and the float members only names.  
> 
> It probably could be made work by allowing NULL names in a
> PyStructSequence_Field. I'll try to do this.

That sounds good to me.  Or you could "subclass" the PyStructSequence
class with something that special-cases the st_?time attributes.

--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