This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author rhettinger
Recipients ctheune, rhettinger
Date 2009-03-09.10:15:34
SpamBayes Score 0.00092749886
Marked as misclassified No
Message-id <1236593737.34.0.13159222197.issue5457@psf.upfronthosting.co.za>
In-reply-to
Content
This appears to be an intrinsic limitation built into a zipfile's
standard file header format.  The header conforms to
http://www.pkware.com/documents/casestudies/APPNOTE.TXT where the date
and time fields are specified to be stored in the MS-DOS standard
date/time format detailed at
http://www.vsft.com/hal/dostime.htm.  In that format, there are only
five bits allocated for seconds.  Accordingly, seconds are stored
without their least significant bit (see the first few lines of
Zipfile.Fileheader where the seconds are encoded with dt[5] // 2).  Upon
decoding, the seconds are scaled back up (see the _RealGetContents()
method where the decoding is (t&0x1F) * 2).

Since zipfiles are supposed to be cross-platform and the file-format is
fixed, I don't see a way to remove this restriction.  Recommending to
close as wont-fix.
History
Date User Action Args
2009-03-09 10:15:38rhettingersetrecipients: + rhettinger, ctheune
2009-03-09 10:15:37rhettingersetmessageid: <1236593737.34.0.13159222197.issue5457@psf.upfronthosting.co.za>
2009-03-09 10:15:35rhettingerlinkissue5457 messages
2009-03-09 10:15:34rhettingercreate