not opening vaex file (h5vaex False) -- can't find a bug and no error message about vaex HOT 4 CLOSED

For some reasons pip or conda did not install the git master properly and obtained an old version of at least vaex/file/other.py.

It seems corrected after forcing installation.
However, I suggest to raise an exception when no format was found.

from vaex.

Hi Morgan,

there are two issues here, one is a change in file format (the latest git has a better format that allows masked values), but it still understands the older format, and that you've resolved yourself.
The second issue is that if it fails to open a file, it will return None. The reason is that every reader is tried, so if the hdf5 one fails, it will try others and does not know for instance that a file should be able to be opened with the hdf5 reader but due to some bug failed to.

I think a better behaviour would be:

• have a file extension to reader mapping, so .hdf5 will be tried by that specific class
• if it fails, it will try all the others
• and if that still didn't get to anything, it will print out the stacktrace by the initial attempt of opening the file

Do you agree?

cheers,

Maarten

from vaex.

I don't know if you want to check the extension itself. Sounds a good idea to try.
I suggested to raise an issue if none of the readers work. Of course that does not fully says why, but at least would not a code run with a None object.

from vaex.

Fixed in master a while ago.

from vaex.