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 alanmcintyre
Recipients NewerCookie, alanmcintyre, ronaldoussoren
Date 2009-09-06.21:26:50
SpamBayes Score 7.2740147e-12
Marked as misclassified No
Message-id <1252272412.33.0.510923135582.issue6839@psf.upfronthosting.co.za>
In-reply-to
Content
Sorry about the confusion--I think I confused myself by looking at the
bit about CRC checksums in the "Info-ZIP Unicode Path Extra Field"
section before I posted.  I meant to say that the central directory name
looks preferred over the per-file header.

n section J, under "file name (Variable)" there's a bit that says:

"If input came from standard input, there is no file name field.  If
encrypting the central directory and general purpose bit flag 13 is set
indicating masking, the file name stored in the Local Header will not be
the actual file name.  A masking value consisting of a unique
hexadecimal value will be stored."

So in these cases the central directory name has to be used.  And, as
you pointed out, some operations like "deleting" a member from the
archive are implemented by editing the central directory, so it would
seem that the central directory should be used if there's a conflict.
History
Date User Action Args
2009-09-06 21:26:53alanmcintyresetrecipients: + alanmcintyre, ronaldoussoren, NewerCookie
2009-09-06 21:26:52alanmcintyresetmessageid: <1252272412.33.0.510923135582.issue6839@psf.upfronthosting.co.za>
2009-09-06 21:26:51alanmcintyrelinkissue6839 messages
2009-09-06 21:26:50alanmcintyrecreate