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 neologix
Recipients mboquien, neologix, pitrou, sbt
Date 2014-04-03.06:14:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAH_1eM1zpVoTq5zvSax5cdiYOk1ycPFKeVg7=L=peU85SAjq0g@mail.gmail.com>
In-reply-to <1396476813.46.0.278551743169.issue21116@psf.upfronthosting.co.za>
Content
> If I remember correctly the problem is that some OS like linux (and
probably others) do not really allocate space until something is written.
If that's the case then the process may get killed later on when it writes
something in the array.

Yes, it's called overcommitting, and it's a good thing. It's exactly the
same thing for memory: malloc() can return non-NULL, and the process will
get killed when first writing to the page in case of memory pressure.
History
Date User Action Args
2014-04-03 06:14:09neologixsetrecipients: + neologix, pitrou, sbt, mboquien
2014-04-03 06:14:09neologixlinkissue21116 messages
2014-04-03 06:14:08neologixcreate