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

Interface improvements for dask and dtype handling #3854

Merged
merged 8 commits into from Jul 29, 2019

Conversation

@philippjfr
Copy link
Contributor

commented Jul 25, 2019

  • Adds an Interface.dtype method to inspect dtypes without loading data
  • Adds Interface.values compute argument to access dask arrays without loading them into memory

@philippjfr philippjfr force-pushed the philippjfr/interface_dtype branch from 3f78d55 to 3d59d38 Jul 25, 2019

@philippjfr

This comment has been minimized.

Copy link
Contributor Author

commented Jul 29, 2019

The changes here are all pretty straightforward so I'm going to merge so I can start on the issue I was actually hoping to fix, which is optimizing range computations.

@philippjfr philippjfr merged commit bb3dc49 into master Jul 29, 2019

4 checks passed

continuous-integration/appveyor/pr AppVeyor build succeeded
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
continuous-integration/travis-ci/push The Travis CI build passed
Details
coverage/coveralls Coverage remained the same at 87.817%
Details

@philippjfr philippjfr deleted the philippjfr/interface_dtype branch Aug 5, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.