Broadly, the problem is that its syntax was meant to reflect that of Matlab, which, I guess, makes it intuitive for Matlab users. For the rest of us, it's mostly unintuitive and inconsistent.
Broadly, the problem is that its syntax was meant to reflect that of Matlab, which, I guess, makes it intuitive for Matlab users. For the rest of us, it's mostly unintuitive and inconsistent.
I would be genuinely interested what are the inconsistency from a Python-perspective.
I am former Matlab/Octave user. To me the julia interface of matplotlib is actually quite nice to use, but unfortunately the installation is a bit brittle.
Some settings only exposed to figure class but not the ax class. And when you are doing stuff towards ax class, you must write
ax.set_ylim(0,3)
instead of
ax.ylim(0,3)
Matplotlib.pyplot is known for its nonsensical api.
By the way, who came up with the idea that an axis object is a great handle to handle subplot settings..?