-
Notifications
You must be signed in to change notification settings - Fork 15
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
Dask type checking #643
Dask type checking #643
Conversation
…data types to a numpy generic (e.g. a scalar, such as int or float) rather than to an array of such things. This change modifies the test to incorporate a union type of array and generic in assert statements for dask operations
This PR still needs review, but is a safe change and is needed to restore test compliance so that others can test their changes. I will re-open the issue and ensure a review occurs before the next release. |
Thanks @tennlee, this seems reasonable. Can you explain why these changes are only needed for some of the dask tests, but not all? |
Great, thanks for checking through it. I only fixed test cases which were failing. I imagine the only tests that were affected are the ones which are calculating a single number, whereas many of the tests are creating arrays which are then still array types. |
Okay that makes sense. I can see that the ones that didn't need changing preserve a dim in the calculation |
Dask type checking
* Allow use of slightly earlier pandas versions * Merge pull request #643 from tennlee/dask_type_checking Dask type checking
With the most recent updates to numpy, the computed dask objects have a different numpy type. I have made the type checking in the automated tests more generic to allow for a range of numpy types in the computed object. This should be compatible across a wide range of Python and numpy versions while still being a correct test.