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 vinay.sajip
Recipients Arfrever, amaury.forgeotdarc, benjamin.peterson, georg.brandl, vinay.sajip
Date 2011-06-19.15:43:10
SpamBayes Score 2.0727253e-11
Marked as misclassified No
Message-id <1308498191.86.0.698855233158.issue12291@psf.upfronthosting.co.za>
In-reply-to
Content
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);
        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)

line. It's not an EOF condition thing, necessarily: I do get expected behaviour at least sometimes when seeking to the end of file.
History
Date User Action Args
2011-06-19 15:43:11vinay.sajipsetrecipients: + vinay.sajip, georg.brandl, amaury.forgeotdarc, benjamin.peterson, Arfrever
2011-06-19 15:43:11vinay.sajipsetmessageid: <1308498191.86.0.698855233158.issue12291@psf.upfronthosting.co.za>
2011-06-19 15:43:11vinay.sajiplinkissue12291 messages
2011-06-19 15:43:10vinay.sajipcreate