just to give you an idea of the speed up:
a 3.3 mb zip file extracted using the current all-python implementation on my machine (win xp 1.67Ghz 1.5GB)
takes approximately 38 seconds.
the same file when extracted using c implementation takes 0.4 seconds.
On Sun, Aug 30, 2009 at 6:35 PM, <email@example.com> wrote:
On 12:59 pm, firstname.lastname@example.org wrote:Given that the use case is "protect my biology homework from my little brother", how fast does the implementation really need to be? áIs speeding it up from 0.1 seconds to 0.001 seconds worth the potential new problems that come with more C code (more code to maintain, less portability to other runtimes, potential for interpreter crashes or even arbitrary code execution vulnerabilities from specially crafted files)?
On Sun, 30 Aug 2009 06:55:33 pm Martin v. L÷wis wrote:
> Does it sound worthy enough to create a patch for and integrate
> into python itself?
Probably not, given that people think that the algorithm itself is
I would think that for most people, the threat model isn't "the CIA is
reading my files" but "my little brother or nosey co-worker is reading
my files", and for that, zip encryption with a good password is
probably perfectly adequate. E.g. OpenOffice uses it for
Given that Python already supports ZIP decryption (as it should), are
there any reasons to prefer the current pure-Python implementation over
a faster version?
Python-Dev mailing list