blaze / blaze/datashape

to_numpy should have strict kwarg and warn rather than err

Open
#106 4 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Python
Stars
189
Forks
62
PR merge metrics
No merged PRs in 30d

Description

Converting datashapes with missing types to numpy dtypes raises an error. This is appropriate because numpy dtypes don't support missing values. It might be nice to control this behavior with a `strict` keyword that allows lowering instead to the non-missing equivalent, e.g.

```
?int32 -> np.int32
```

Perhaps we should raise a warning rather than an error in this case?

What should be default behavior?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.