This is not to discredit the LIAC-ARFF reader, as I think it is useful tool that allows for parsing and unparsing of many arff files that surve a broad purpose.

However, today I discovered a bug (strings with quotes and escape characters, we use this for storing arff traces) which required me to dive into the code. We currently use it for serializing arffs to disk (either to local disk, but also to upload to OpenML). Basically, it serializes arff files in a nice way, but deserializing goes wrong.

Given the following facts:
a) It seems that active development has stopped in 2015 judging by the commits
b) The code builds upon a set of regular expressions (which is great for efficiency, but hard to adapt without the proper knowledge)
c) The unit tests are not as extensive as I would expect them to be (although this is something we can change, of course)

I can't help but wonder whether it wouldn't be better to switch to the scipy variant. We discussed this before, what were the pro's and cons again?