0.0.14

[azazellochg]

Add shlex kwarg for parsing multi-item fields (@jamesmkrieger). False by default as it slow down parsing (e.g. iterRows) by a lot.

[delarosatrevin]

Thanks @jamesmkrieger for the improvement! Is there any difference (in speed or results) when using shlex? I don't like to let the option to use it or not to the user (developer) of the emtable API. I think one should always get the correct results and not think if your table will contain quoted values. What about if we always use shlex for splitting?

[azazellochg]

Thanks @jamesmkrieger for the improvement! Is there any difference (in speed or results) when using shlex? I don't like to let the option to use it or not to the user (developer) of the emtable API. I think one should always get the correct results and not think if your table will contain quoted values. What about if we always use shlex for splitting?

Shlex, if used by default, slows down our example tests x10 times

[delarosatrevin]

This is a serious slowdown....anyway might be good to be able to handle these cases without shlex.

[azazellochg]

While having quotes as delimiters for the column value is allowed by STAR format, this is the first case I see anybody using them. There are rare cases when relion has "" (empty) values but that's it

[jamesmkrieger]

We actually have another case that made me aware of it in our Zernike3D programs. There’s also another case where we’re thinking of using it.

I guess there won’t be that many others though.

[azazellochg]

Extra kwarg removed, quotes are checked internally now as requested by @delarosatrevin .

[jamesmkrieger]

Looks good to me

[azazellochg]

One more case covered, when the column value is "ggg ggg" and not " ggg ggg "

[delarosatrevin]

Thanks @jamesmkrieger and @azazellochg !