You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Version 3.3 of matplotlib added a deprecation warning for QT4Agg, which seems planned to be deprecated in 3.5. If I'm understanding correctly how things work, that would mean from 3.5 that this call in gui.py: from matplotlib.backends.backend_qt4agg import FigureCanvasQTAgg as FigureCanvas4
will throw an error. Changing this:
from matplotlib.backends.backend_qt4agg import FigureCanvasQTAgg as FigureCanvas4
from matplotlib.backends.backend_qt5agg import FigureCanvasQTAgg as FigureCanvas5
def FigureCanvas(fig):
try:
return FigureCanvas5(fig)
except Exception:
return FigureCanvas4(fig)
to this:
try:
from matplotlib.backends.backend_qt5agg import FigureCanvasQTAgg as FigureCanvas
except Exception:
from matplotlib.backends.backend_qt4agg import FigureCanvasQTAgg as FigureCanvas
should do the trick. I'm happy to make a pull request with that change if needed/desired.
The text was updated successfully, but these errors were encountered:
It's worth noting that this does now throw an error. I guess viscm isn't actively supported anymore, but would it be possible to just pull #57, @tacaswell or @stefanv or whoever has the power?
Version 3.3 of matplotlib added a deprecation warning for QT4Agg, which seems planned to be deprecated in 3.5. If I'm understanding correctly how things work, that would mean from 3.5 that this call in gui.py:
from matplotlib.backends.backend_qt4agg import FigureCanvasQTAgg as FigureCanvas4
will throw an error. Changing this:
to this:
should do the trick. I'm happy to make a pull request with that change if needed/desired.
The text was updated successfully, but these errors were encountered: