type('')==bytes evaluates to True in Python2, and False in Python3. This
was causing some variable to never be set, which eventually led to
various silent errors downstream; the ultimate result was the
uncertainty values not being properly loaded from the data, which caused
all features which used those to have the wrong values.
Thanks, Brett! I'm going to merge this for now. In the long run, we should probably get rid of all such types of checks. I cannot see why we would need them.
type('')==bytes
evaluates toTrue
in Python2, andFalse
in Python3. This was causing some variable to never be set, which eventually led to various silent errors downstream; the ultimate result was the uncertainty values not being properly loaded from the data, which caused all features which used those to have the wrong values.