Thanks to visit codestin.com
Credit goes to github.com

Skip to content

What are np.int0 and np.uint0 supposed to be? #11025

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

Closed
eric-wieser opened this issue May 1, 2018 · 3 comments
Closed

What are np.int0 and np.uint0 supposed to be? #11025

eric-wieser opened this issue May 1, 2018 · 3 comments

Comments

@eric-wieser
Copy link
Member

Some archaelogy shows that 618a8d4 seems to have taken it from Numeric, which provided Int0.

Numeric's IntN seemed to mean meaning C99s int_leastN_t, suggesting that Int0 should be signed char.

So why is np.int0 an alias of np.intp?

@rkern
Copy link
Member

rkern commented May 1, 2018

In Numeric, Int0 is indeed equivalent to Int8. There's no real reason for it to exist at all, though, fixed or unfixed. I don't recommend using it. Or letting its anomalous existence bother you much. :-)

@seberg
Copy link
Member

seberg commented Jan 15, 2020

I will close this in favor of the new gh-15334 (renaming it as a documentation and/or deprecation) not that it matters which one is open. Included the info about int8 there.

@seberg seberg closed this as completed Jan 15, 2020
@ramenspazz
Copy link

But if there is no reason for it to exist, can I delete it safely? I don't want things with no purpose even if you want me to keep them if they have no purpose...

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

4 participants