➜

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 Amund Hov
Recipients Amund Hov
Date 2015-08-05.09:43:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1438767812.67.0.706553781663.issue24794@psf.upfronthosting.co.za>
In-reply-to
Content 
In my project I have a mixture of scripts using Python 2.7 and 3.4.
Some of the scripts using python 3.4 are packaged into archives using
PyZipFile.

Through some combination I ended up with 2.7 compiled packages in my archive when packaging using python 3.4. In combination with issue 24792 "zipimporter masks import errors" this led to many grey hairs figuring out why my packaging scripts suddenly broke.

Are there sufficient provisions in PyZipFile to prevent this? It seems it will happily mix compiled files with differing magic bytes.
History
Date User Action Args
2015-08-05 09:43:32Amund Hovsetrecipients: + Amund Hov
2015-08-05 09:43:32Amund Hovsetmessageid: <1438767812.67.0.706553781663.issue24794@psf.upfronthosting.co.za>
2015-08-05 09:43:32Amund Hovlinkissue24794 messages
2015-08-05 09:43:32Amund Hovcreate