Comment 24 for bug 1185701

I have encountered this bug (ubuntu box, lxml 3.x version). Besides that
I encounered another bug which seems to be related: elem.getnext()
returnes None despite elem having a sibling beneth it. Unfortunately
I encountered this while using a big and private xml file which I can
not share.

The issue with getnext() seems related to this one becuase the workaround
suggested in this ticket (using StringIO instead of file object) solved
both of my issues.