I can put the old behavior back if necessary, but 1) we should never encounter this condition, and 2) it was errantly coded before. Specifically, now that we allow two dtypes (float64 and complex128), if the "skip" had ever been read, we would have assumed "dtype=float64" because of the construction with `ones=np.zeros()` (old line 1411). This would have thrown an error if we had read the "skip" in a raw file that had complex data stored. But as I said, we should never hit that condition anyway...