FutureWarning: Using a non-tuple sequence for multidimensional indexing is deprecated
See original GitHub issueIt’s just a deprecation warning, but it should be use to fix it
/Library/Python/2.7/site-packages/scipy/signal/signaltools.py:2383: FutureWarning: Using a non-tuple sequence for multidimensional indexing is deprecated; use `arr[tuple(seq)]` instead of `arr[seq]`. In the future this will be interpreted as an array index, `arr[np.array(seq)]`, which will result either in an error or a different result.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Using a non-tuple sequence for multidimensional indexing is ...
... FutureWarning: Using a non-tuple sequence for multidimensional indexing is deprecated; use `arr[tuple(seq)]` instead of `arr[seq]`.
Read more >Suggestion in warning message about non-tuple indexing ...
FutureWarning : Using a non-tuple sequence for multidimensional indexing is deprecated; use arr[tuple(seq)] instead of arr[seq] .
Read more >Using a non-tuple sequence for multidimensional indexing is ...
Pandas : FutureWarning : Using a non-tuple sequence for multidimensional indexing is deprecated use `arr[tuple(seq)]` [ Beautify Your ...
Read more >FutureWarning w/ SpatialDataFrame - Esri Community
Hello All, I'm getting the following FutureWarning when using the ... a non-tuple sequence for multidimensional indexing is deprecated; use ...
Read more >FutureWarning: Using a non-tuple sequence for multidimensional ...
FutureWarning : Using a non-tuple sequence for multidimensional indexing is deprecated use `arr[tuple(seq)]`. data = np.genfromtxt(Example.csv, delimiter = ' ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Scipy 1.2 was released via pip now. If you take the Wave-U-Net virtualenv and upgrade your scipy package via
to install the new 1.2 version, can you verify that this warning disappears?
This is an issue within the scipy library, so I have pretty much nothing to do with this. It seems other people have similar issues, an there is a problem in general with scipy versions below 1.2, see here
I noticed that we are using scipy 1.1 and so probably this will be fixed by updating to 1.2, however it is not available via pip as far as I can tell, so I think we are going to have to ignore it for now.
I am going to leave the issue open so that when scipy 1.2 comes out I will remember to try to update the project to that.
Thanks for reporting.