The cufflinks module on pip does not have the fix accounting for pandas deprecating pandas.np. There are two possible solutions for this.
a) Fix it yourself: open the pip cufflinks module in your environment folder and replace all occurrences of pandas.np with np, after importing numpy as np at the top of the file in plotlytools.py.
b) Replace the plotlytools.py file in your cufflinks folder with the one in this github repo, which has the required fixes.
Spreads are not labelled consistently if the first column has consistently greater values than the second column. If this is the case, both the graph labels and values for yaxis2 are incoherent, and the spread approximates a right triangle shape. The solution for this appears to be changing the order of your columns to have the largest one first.
Data starting from 2018-01-12 is visualized normally because there exists at least one data point for which the first element in the ordered pair of columns is greater than the second element:
For data starting from 2018-01-13, when this is no longer true the issue manifests itself:
I am reporting two issues:
The cufflinks module on pip does not have the fix accounting for pandas deprecating pandas.np. There are two possible solutions for this.
a) Fix it yourself: open the pip cufflinks module in your environment folder and replace all occurrences of
pandas.np
withnp
, after importing numpy asnp
at the top of the file inplotlytools.py
.b) Replace the
plotlytools.py
file in your cufflinks folder with the one in this github repo, which has the required fixes.Spreads are not labelled consistently if the first column has consistently greater values than the second column. If this is the case, both the graph labels and values for
yaxis2
are incoherent, and the spread approximates a right triangle shape. The solution for this appears to be changing the order of your columns to have the largest one first.Data starting from 2018-01-12 is visualized normally because there exists at least one data point for which the first element in the ordered pair of columns is greater than the second element:
For data starting from 2018-01-13, when this is no longer true the issue manifests itself: