[Python-Dev] float atime/mtime/ctime - a bad idea? (original) (raw)
Martin v. Loewis martin@v.loewis.de
16 Oct 2002 16:28:04 +0200
- Previous message: [Python-Dev] float atime/mtime/ctime - a bad idea?
- Next message: [Python-Dev] float atime/mtime/ctime - a bad idea?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Guido van Rossum <guido@python.org> writes:
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.
Regards, Martin
- Previous message: [Python-Dev] float atime/mtime/ctime - a bad idea?
- Next message: [Python-Dev] float atime/mtime/ctime - a bad idea?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]