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 Kevin Ar18
Recipients Kevin Ar18, gregory.p.smith, loewis
Date 2007-08-30.15:43:53
SpamBayes Score 0.44350767
Marked as misclassified No
Message-id <1188488633.85.0.256139868374.issue1060@psf.upfronthosting.co.za>
In-reply-to
Content
Just some thoughts....
In posting about this problem elsewhere, it has been argued that you
shouldn't be copying that much stuff into memory anyways (though there
are possible cases for a need for that).
However, the question is what should the zipfile module do.  At the very
least it should account for this 2GB limitation and say it can't do it.
 However, how it should interact with the programmer is another
question.  In one of the replies, I am told that strings have a 2GB
limitation, which means the zipfile module can't be used in it's current
form, even if fixed.  Does this mean that the zipfile module needs to
add some additional methods for incrementally getting data and writing
data?  Or does it mean that programmers should be the ones to program an
incremental system when they need it... Or?
History
Date User Action Args
2007-08-30 15:43:53Kevin Ar18setspambayes_score: 0.443508 -> 0.44350767
recipients: + Kevin Ar18, loewis, gregory.p.smith
2007-08-30 15:43:53Kevin Ar18setspambayes_score: 0.443508 -> 0.443508
messageid: <1188488633.85.0.256139868374.issue1060@psf.upfronthosting.co.za>
2007-08-30 15:43:53Kevin Ar18linkissue1060 messages
2007-08-30 15:43:53Kevin Ar18create