Benjamin Peterson <benja...@python.org> added the comment:
2011/6/19 Vinay Sajip <rep...@bugs.python.org>:
>
> Vinay Sajip <vinay_sa...@yahoo.co.uk> added the comment:
>
> This seems a bit hacky, and I'm not sure how reliable it is. I added this
> after the read_object call:
>
> if (is_file) {
> PyObject * newpos;
> int cp, np;
>
> cp = ftell(rf.fp);
> newpos = PyObject_CallMethod(f, "seek", "ii", cp, SEEK_SET);
Why not 0?
> assert(newpos != NULL);
> np = PyLong_AsLong(newpos);
> Py_DECREF(newpos);
> assert(cp == np);
> }
>
> When I run the code lots of times, I sometimes get assertion failures at the
>
> assert(newpos != NULL)
That's because the call is failing. Why?
>
> line. It's not an EOF condition thing, necessarily: I do get expected
> behaviour at least sometimes when seeking to the end of file.
>
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue12291>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
