CJ Kucera wrote:
> Hello list, resurrecting a rather old thread from here:
>
> http://mail.python.org/pipermail/python-dev/2009-August/091450.html
... and one final update from me, mostly just so Google and the like
will pick it up. I did actually end up packaging up something I called
"czipfile
Hello list, resurrecting a rather old thread from here:
http://mail.python.org/pipermail/python-dev/2009-August/091450.html
I've actually come across a use case where faster zipfile decryption
would be very helpful to me (though one could certainly argue that it's
a frivolous case). I'm writing
On Mon, Aug 31, 2009 at 12:08 PM, Gregory P. Smith wrote:
>
>
> On Sun, Aug 30, 2009 at 10:40 PM, Jeroen Ruigrok van der Werven <
> asmo...@in-nomine.org> wrote:
>
>> -On [20090831 06:29], Collin Winter (coll...@gmail.com) wrote:
>> >Are there any applications/frameworks which have zip files on t
On Sun, Aug 30, 2009 at 10:40 PM, Jeroen Ruigrok van der Werven <
asmo...@in-nomine.org> wrote:
> -On [20090831 06:29], Collin Winter (coll...@gmail.com) wrote:
> >Are there any applications/frameworks which have zip files on their
> >critical path, where this kind of (admittedly impressive) speed
-On [20090831 06:29], Collin Winter (coll...@gmail.com) wrote:
>Are there any applications/frameworks which have zip files on their
>critical path, where this kind of (admittedly impressive) speedup
>would be beneficial? What was the motivation for writing the C
>version?
Would zipped eggs count?
On Sun, Aug 30, 2009 at 7:34 AM, Shashank
Singh wrote:
> 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 implementa
exar...@twistedmatrix.com 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 t
On 30 aug 2009, at 16:34, Shashank Singh wrote:
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
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.
--shashank
On Sun, Aug 30, 2009 at 6:35 P
On 12:59 pm, st...@pearwood.info wrote:
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
fairly useless.
I would think that for most
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
> fairly useless.
I would think that for most people, the threat model isn't "th
> 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
fairly useless.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.pyth
Hi All,
I have implemented the simple zip decryption in C (yes, the much loathed
weak password based classical
PKWARE encryption, which incidentally is the only one currently supported in
python) .
It performs fast, as one would expect, as compared to the current all-python
implementation.
Does
13 matches
Mail list logo