Closed rout39574 closed 1 year ago
Thanks, but I wonder which version of matplotlib you are running, can you please share? I'm afraid this change may break things for people on a different mpl version. Maybe if you can share the json data for me to reproduce the issue (louwrentius@gmail.com if you don't want to post it here) that might be interesting as I've not seen this error ever.
P.s. my response may be delayed
I'll find this and give you data tomorrow. It was a brand new install, so matplotlib drift is not ridiculous.
Ok I haven't looked at it but it may be worse: there was a new matplotlib version released that may break fio-flot. So this issue may be related to this and that means if I would merge this fix people on older versions have an issue.
Here are the packages in my venv
contourpy==1.0.5 cycler==0.11.0 fio-plot==1.0.21 fonttools==4.37.2 Jinja2==3.1.2 kiwisolver==1.4.4 MarkupSafe==2.1.1 matplotlib==3.6.0 numpy==1.23.3 packaging==21.3 Pillow==9.2.0 pyan3==1.2.0 pyparsing==3.0.9 python-dateutil==2.8.2 six==1.16.0
My read is that passing ax is the non-breaking technique that they recommended. Here's the 3.4 - 3.5 comment on how to avoid problems,
https://github.com/matplotlib/matplotlib/blob/v3.5.x/lib/matplotlib/figure.py
Seems to me that adding the ax= attribute isn't likely to break anyone's backlevel; that arg is present back to 2.2
Thanks and sorry for the extreme delay.
Heya. I found fio-plot to crash.
I followed the suggestion and added an ax argument.