From a user (py2.3.4 based app) I got only this small
trace:
I cannot reproduce it easily:

  --- sync complete: 6 files (0+6), 3488210kB copied. 
  --- 1795.9 Seconds (100.0% CPU Time) 
  Exception exceptions.OverflowError: 'long int too
large to convert to int' in <bound method
ZipFile.__del__ of <zipfile.ZipFile instance at
0x009D9D50>> ignored

Logged In: YES 
user_id=1115903

How do you reproduce it?  I have seen that exception pop up
when trying to add a file >2GB to an archive (although in
that case it occurred during the call to ZipFile.write
rather than __del__).  It looks to me like writing the
end-of-zip-archive record - during close(), which is called
by __del__() -  would give this exception if the contents of
the archive were > 2GB, but I haven't tried this out to be
sure.  If that's what's causing the problem, then it would
appear to me that it's just a limitation of the ZIP file
format, but maybe the ZipFile object could detect this and
raise a less cryptic exception.

Logged In: YES 
user_id=1115903

Oh, silly me, I didn't notice this: "3488210kB copied,"
which is of course >2GB (don't know if your number indicates
pre- or post-compression though). I'm assuming this means
that you're bumping into the limits of the zip file format.

Since this sort of thing happens occasionally in some
applications I maintain, I will look at making a patch for
ZipFile that will at least tell you when you exceed file
format limits (either individual file size or total archive
file size).

At the time, zipfile.py did not support the ZIP64 format...