Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Categorical optimization #229

Open
gbrener opened this issue Aug 3, 2017 · 0 comments
Open

Categorical optimization #229

gbrener opened this issue Aug 3, 2017 · 0 comments

Comments

@gbrener
Copy link

gbrener commented Aug 3, 2017

As the odo issue blaze/odo#561 mentions, a bottleneck emerged with respect to datashape.Categorical instantiation pointing to this line, where the constructor coerces the input categories into a tuple. I wonder whether we should relax this constraint for Categorical objects, such that we could represent the underlying categories as numpy arrays, i.e. Series.cat.categories.values, and speed up datashape with respect to pandas/dask categorical discovery. cc @jbednar @teoliphant

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant