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 pitrou
Recipients Matt.Mackall, benjamin.peterson, ezio.melotti, josh.r, larry, loewis, ncoghlan, pitrou
Date 2014-04-13.16:43:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1397407425.3.0.630526037792.issue21199@psf.upfronthosting.co.za>
In-reply-to
Content
> Antoine: Inability to perform a 2GB+ read properly is not something
> that should be worked around on a case by case basis.

Really we are talking about Python 2.7 here. Anyone having this problem *has* to work it around in order for their code to work on published versions. The benefit of fixing this in the next 2.7.x iteration is small compared to the cost of a potential regression in the core I/O implementation.
History
Date User Action Args
2014-04-13 16:43:45pitrousetrecipients: + pitrou, loewis, ncoghlan, larry, benjamin.peterson, ezio.melotti, Matt.Mackall, josh.r
2014-04-13 16:43:45pitrousetmessageid: <1397407425.3.0.630526037792.issue21199@psf.upfronthosting.co.za>
2014-04-13 16:43:45pitroulinkissue21199 messages
2014-04-13 16:43:45pitroucreate