I've been using the following lambda/function for a number of months now
(I got the idea from someone in #python, though I don't remember who):
def chop(s, n):
"""Chops a sequence, s, into n smaller tuples."""
return zip(*[iter(s)] * n)
...or...
chop = lambda s, n: zip(*[iter(s)
On Sat, 2006-05-27 at 06:22 +1000, John Machin wrote:
> On 27/05/2006 2:54 AM, Jeremy L. Moles wrote:
>
> ["chop" snipped]
>
> >
> > Furthermore, what do people think about the idea of adding a truly
> > empty, no-op global lambda somewhere in Python? I
I have an object (written as part C extension, part pure Python) called
foo that I've been using without much fuss for a few months now.
However, in my latest project (a rather large one involving
multi-threading, pygtk, etc.), I'm seeing some really strange behavior
with a particular instance of m
Hey Fredrik, thanks for responding. :) Your posts are always helpful and
informative!
On Wed, 2006-03-08 at 15:41 +0100, Fredrik Lundh wrote:
> Jeremy L. Moles wrote:
>
> >I have an object (written as part C extension, part pure Python) called
> > foo that I've been using
