-
-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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
Regression in numpy.insert() when axis != None #392
Milestone
Comments
87
added a commit
to 87/numpy
that referenced
this issue
Sep 7, 2012
This should fix the problems with numpy.insert(), where the input values were not checked for all scalar types and where values did not get inserted properly, but got duplicated by default.
certik
pushed a commit
to certik/numpy
that referenced
this issue
Sep 13, 2012
This should fix the problems with numpy.insert(), where the input values were not checked for all scalar types and where values did not get inserted properly, but got duplicated by default.
I think this is now fixed. |
luyahan
pushed a commit
to plctlab/numpy
that referenced
this issue
Apr 25, 2024
feat: Add vminv[q]_[s8|s16|s32|u8|u16|u32|f32|f64]
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I believe that the fix to Ticket #808 has caused a regression in numpy.insert()
This is the commit
Previously:
gave:
now it gives
I don't think is the correct result.
Also issue #378 is a result of same change
The text was updated successfully, but these errors were encountered: