Stijn De Weirdt wrote:
> but the following code gives a segfault instead of an IOerror
> fname='test123'
> f=open(fname,'w')
> f.read()
I've tracked this down to r67740:
"""
Issue #1706039: Support continued reading from a file even after
EOF was hit.
"""
Looking at the diff, I question the corr
s...@pobox.com wrote:
> Did this not happen with 2.5.2?
I have 2.5.1 and 2.5.2 and it produces an IOError, just as it should. So
this was indeed introduced by 2.5.3.
-Scott
--
Scott Dial
sc...@scottdial.com
scod...@cs.indiana.edu
___
Python-Dev mailin
s...@pobox.com schrieb:
> Stijn> any hints what might cause this (or how i can figure it out). i
> Stijn> have a coredump, but have no clue what to look for.
>
> I can reproduce it on my Mac. The croak happens while it is attempting to
> raise the exception about a bad file descriptor. U
Stijn> any hints what might cause this (or how i can figure it out). i
Stijn> have a coredump, but have no clue what to look for.
I can reproduce it on my Mac. The croak happens while it is attempting to
raise the exception about a bad file descriptor. Unfortunately, in
PyErr_Restore th
hi all,
i'm trying to build python 2.5.3 on centos5.2 x86_64 (base gcc is
4.1.2)
output of env, configure, make -j and make test at
http://users.ugent.be/~stdweird/python-gcc-seg.tar.gz
this all seems ok (at least to me ;)
but the following code gives a segfault instead of an IOerror
fname='te
