Cannot open xpt files with the latest xport dependency version about visidata HOT 2 OPEN

Thanks for pointing this out, @v.

It appears that visidata relies on behavior from xport v2, and xport v3 has changed how to read files:

v3.0.0, 2020-04-20
Revise API to the load/dump pattern. Enable specifying dataset name, variable names, labels, and formats.

Perhaps visidata should switch to using xport v3's load() for reading files.

As a side note, while investigating the xport v2 format, I noticed the .xpt loader has a bug. It will cause inability to edit cells, and possibly odd behavior when selecting rows. I've proposed a fix here: #2365
If you run into such problems, you may want to apply that fix. If not, an alternate workaround would be to save .xpt files right after opening them, in some other format (like .tsv or .json). Then reopen the new .tsv file in visidata.

from visidata.

I've drafted a fix to update visidata's use of xport from xport v2 to v3.6.1. I'm unfamiliar with SAS and Pandas, so I cannot test it thoroughly. But it does seem to give the same results as Visidata v3.0 for this 2-column test file of numbers: https://github.com/prasertcbs/basic-dataset/blob/8c80eb454b2defd3db217d8f95883eb6a1e3f263/brakes.xpt.

I'll leave the draft here as a starting point for anyone who wants to work with it in the future: 793ec73

from visidata.