errors in python and yajl2_c backends about ijson HOT 2 CLOSED

@Bubu thanks again for getting in touch and the details in the report.

The problem is exactly one that you suspect: your file-object from libarchive is "weird" in the sense that when it gets to the endof the file it implicitly returns None instead of an empty string (here and here). File-like objects are expected to return an empty string ('' or b'', depending on the mode with which it operates) when the end of the file is reached. This is the behavior that ijson expects as well, although clearly different backends are more or less strict about this (some do something like if not buffer, in which case None just works, but others are not that lenient), which is why some fail and some others don't.

I'd say this is not a bug on our end, but something that will need to be corrected in python-libarchive. In the meanwhile you'll have to wrap their EntryReadStream class into your own and provide the None -> b'' conversion yourself if you want to continue down that route.

Based on this, I'll mark this issue as "invalid" and will close it, but I'm happy to continue the discussion if needed.

from ijson.

Thanks for the detailed explanation. I'll see about opening an issue with python-libarchive.

from ijson.