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 sbt
Recipients brian.curtin, jcea, mark.dickinson, pitrou, sbt, schlamar, serhiy.storchaka, terry.reedy, tim.golden
Date 2013-01-28.00:29:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
On 27/01/2013 8:27pm, Terry J. Reedy wrote:
> I agree we do not need to retain unpredictable 'dumb luck' -- in
> future versions. But in the absence of a clear discrepancy
> between doc and behavior (the definition of a bug) I believe
> breaking such code in a bugfix release would be contrary to
> current policy.

Currently if you mmap a file with length 4GB+1, then you get an mmap of 
length 1.  Surely that is a *huge* discrepancy between docs and behaviour.

BTW, on 32 bit Windows it looks like the maximum size one can mmap in 
practice is about 1.1GB:

PS> python -c "import mmap; m = mmap.mmap(-1, int(1.1*1024**3))"
PS> python -c "import mmap; m = mmap.mmap(-1, int(1.2*1024**3))"
Traceback (most recent call last):
   File "<string>", line 1, in <module>
WindowsError: [Error 8] Not enough storage is available to process this 
Date User Action Args
2013-01-28 00:29:18sbtsetrecipients: + sbt, terry.reedy, jcea, mark.dickinson, pitrou, tim.golden, brian.curtin, schlamar, serhiy.storchaka
2013-01-28 00:29:18sbtlinkissue16743 messages
2013-01-28 00:29:18sbtcreate