-
-
Notifications
You must be signed in to change notification settings - Fork 11k
pad in arraypad.py changed behavior in an undocumented fashion #7353
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
Comments
Closed
This comment is relevant to this bug: #7354 (comment) |
chiffa
added a commit
to chiffa/numpy
that referenced
this issue
Feb 27, 2016
chiffa
added a commit
to chiffa/numpy
that referenced
this issue
Feb 27, 2016
chiffa
added a commit
to chiffa/numpy
that referenced
this issue
Feb 28, 2016
This test exposes padding bug described in the issue numpy#7353
chiffa
added a commit
to chiffa/numpy
that referenced
this issue
Feb 28, 2016
Constant padding on 4 sides of a 2d array expected a numpy ndarray, and not a ndarray like (tuple, list, ...) Detailed description is in the issue numpy#7353
njsmith
added a commit
that referenced
this issue
Feb 28, 2016
BUG: pull request related to the issue #7353
jaimefrio
pushed a commit
to jaimefrio/numpy
that referenced
this issue
Mar 22, 2016
This test exposes padding bug described in the issue numpy#7353
jaimefrio
pushed a commit
to jaimefrio/numpy
that referenced
this issue
Mar 22, 2016
Constant padding on 4 sides of a 2d array expected a numpy ndarray, and not a ndarray like (tuple, list, ...) Detailed description is in the issue numpy#7353
charris
pushed a commit
to charris/numpy
that referenced
this issue
Apr 18, 2016
This test exposes padding bug described in the issue numpy#7353
charris
pushed a commit
to charris/numpy
that referenced
this issue
Apr 18, 2016
Constant padding on 4 sides of a 2d array expected a numpy ndarray, and not a ndarray like (tuple, list, ...) Detailed description is in the issue numpy#7353
Retested with NumPy 1.14.3 and this appears to be fixed. |
2 tasks
@jakirkham Thanks for the heads up. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Previously this command worked:
However in the 1.10.4 it now returns the following stack trace:
This is now the way of implementing the padding:
Could you please add relevant documentation to the
pad
function in thearraypad.py
?An additional issue is that it looks like
np.nan
gets converted to-2147483648
which seems to be overflowing 32-bit signed integer. It does not affect my code that much, but this is an issue you might need to be aware of.The text was updated successfully, but these errors were encountered: