fix deprecation and possible faulty construction of pandas tables #221
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Before this PR pandas tables were being constructed from
Tables.DictColumnTable
using an unordered dict for the columns. This was leading to deprecation warnings as seen here but more importantly, it could result in the creation of table objects which would have content inconsistent with their schema. I'm actually a bit unsure why this was not breaking far more spectacularly (update: it's because the methods provided byDictColumnTable
make the ordering of the dict largely unnecessary, but it would still break if anything ever iterated over the columns in the dict.)I used the
OrderedDict
constructor from withinTables
for this so as not to have to addOrderedCollections
as a dependency.