-
-
Notifications
You must be signed in to change notification settings - Fork 10.8k
Inconsistent concatenate behaviour #5759
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
There is a deprecation warning in place, try this:
It was introduced in 21a1d73 and 4475ead, almost 3 years ago. Perhaps 1.10 could be the deprecated future? |
I guess we should look up when the first NumPy release containing those
|
This comment seems to indicate it went into effect in 1.7. |
Fixed by #8584. Closing. |
Numpy under Python 2.7.9:
I would expect the second use of concatenate to throw an exception, too. Is this behaviour intentional?
The text was updated successfully, but these errors were encountered: