Fix column ordering in Python, null handling for computed columns #907
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.
This PR provides several fixes for issues with
PerspectivePython
:pandas.DataFrame
, Perspective will read thecolumns
property and load the dataframe in the specified order. Perspective will continue to call.keys()
for datasets composed of Pythondict
andlist
values, and the canonical way to determine column order should be through creating aView
with thecolumns
kwarg set. This change simply makes Perspective's column layout more symmetrical with that of the provided DataFrame.View
, columns included inaggregates
but not incolumns
will not have their aggregates applied. This fixes issue Pivoted PerspectiveWidget column order broken in Python 2 #904, which occurred because the order of.keys()
inaggregates
!=the order of
columns`.null
to the output column if any value provided to the computed function isnull
orundefined
.