News for hackers. Stuff that matters.
Re:Gnuplotlib: Non-Painful Plotting for NumPy by fransje26 on Thursday February 01, 2024 @04:02AM (#39214013)
Matplotlib is what is wrong with matplotlib..

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.

Re:Gnuplotlib: Non-Painful Plotting for NumPy by kwertzzz on Thursday February 01, 2024 @04:27AM (#39214136)
Can you give an example of its inconsistency?

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.

Re:Gnuplotlib: Non-Painful Plotting for NumPy by akasakahakada on Thursday February 01, 2024 @08:27AM (#39215677)
Somewhere you can use c="k" for colour but sometimes you cannot, you must use color="k".

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.

Re:Gnuplotlib: Non-Painful Plotting for NumPy by fransje26 on Friday February 02, 2024 @02:44PM (#39233207)
From the top of my head, the one that annoys me regularly is the difference between setting a title/x or range on plot, and on a subplot. So plot.title(), and ax.set_title().

By the way, who came up with the idea that an axis object is a great handle to handle subplot settings..?