Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Clarification about NEP 40: NumPy Scalars and Type Hierarchy

See original GitHub issue

As a side note to the above datatype implementation: unlike the datatypes, the NumPy scalars currently do provide a type hierarchy

Got a little confused by the statement above given that issubclass(np.int64, np.integer). Did it mean to say unlike the python datatypes or unlike the other datatypes instead ?

Issue Analytics

State:
Created 3 years ago
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

sebergcommented, Apr 21, 2020

Well, its the conundrum… Of course from a type (theory, not class) point of view, the elements of an array of >int8 and <int8 are obviously of the same type np.int8 scalars. Maybe you could say the dtype only describes the type (i.e. scalar type/class) to the array. Which is also why you can argue that the dtype itself doesn’t need to have a hierarchy. It doesn’t actually need to serve the purpose of a type (with a hierarchy) since it is strictly associated to a scalar type/class that already has these properties.

Thats kind-of what my last email on the list is about… And no, I do not know for certain what is the “right” way to see it 😃.

0reactions

anirudh2290commented, Jul 13, 2020

Agreed @rossbar ! Closing.