> I believe the idea is that if you run into a MemoryError, in particular
> on linux (whose allocator will give you a nonzero pointer well beyond
> what was actually available), you can't really trust the state of the
> interpreter, so it is expected that Python will be ending shortly.
> Forcing t
Kristján Valur Jónsson <[EMAIL PROTECTED]> wrote:
>
> I just ran some static analysis of the python core 2.5 with Visual Studio
> team system.
> There was the stray error discovered. I will update the most obvious ones.
[snip]
> 2) There is a lot of code that goes like this:
> f->buf = PyMem_R
