-
-
Notifications
You must be signed in to change notification settings - Fork 10.8k
BUG: The input and output of rollaxis
vary in flags.C_CONTIGUOUS and flags.F_CONTIGUOUS
#27855
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
Labels
Comments
reshape
returns different array with different order parameterreshape
returns different arrays with different order parameters
reshape
returns different arrays with different order parametersreshape
returns different arrays with "A"/None
reshape
returns different arrays with "A"/Nonereshape
returns different arrays with ("C"/"A")
reshape
returns different arrays with ("C"/"A")reshape
returns different arrays with (C
/A
) orders
reshape
returns different arrays with (C
/A
) ordersrollaxis
' has the different orders.
rollaxis
' has the different orders.rollaxis
has the different orders.
rollaxis
has the different orders.rollaxis
vary in flags.C_CONTIGUOUS and flags.C_CONTIGUOUS.
rollaxis
vary in flags.C_CONTIGUOUS and flags.C_CONTIGUOUS.rollaxis
vary in flags.C_CONTIGUOUS and flags.F_CONTIGUOUS.
I find that the issue is related to the |
rollaxis
vary in flags.C_CONTIGUOUS and flags.F_CONTIGUOUS.rollaxis
vary in flags.C_CONTIGUOUS and flags.F_CONTIGUOUS
The behavior is correct, since this always returns a view. (Even otherwise, we don't strictly guarantee preserving this anyway, but often it makes sense to either way.) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the issue:
I find that the input and output of
rollaxis
vary in flags.C_CONTIGUOUS and flags.F_CONTIGUOUS.Reproduce the code example:
Error message:
Python and NumPy Versions:
Runtime Environment:
Context for the issue:
I do not find information related to this issue in the doc and can not determine whether this issue is expected or a bug.
The text was updated successfully, but these errors were encountered: