This turned out to be a Pandas dataframe issue that was easily fixed -- for some reason it defaulted the display differently for this column, but the setting was easily changed.