matplotlib’s decision to include MATLAB-like state machine plotting was really stupid. It used to be extremely confusing and I would just write to file and use GNUplot
well what I mean is at least now that Python is being used widely for numerical calculations that there are tutorials that talk about it. When I started using matplotlib in like 2011 it felt like a total mystery.
I’m not saying matplotlib isn’t good for that, I’m saying the pyplot state-based submodule can’t do everything and switching to the OOP interface is jarring and confusing. I mean stuff like customizing tick marks
absolutely, which is why they shouldn’t have made pyplot. Unfortunately its already become so ingrained that it’s the main way to plot stuff in python. I’m probably gonna start using Seaborn or Bokeh or Altair
Isn’t that just if you use matplotlub.pyplot? The underlying API is stateless. The only time I’ve had a problem is with legend(), mostly because I haven’t looked up the underlying API, though I tend to creat the legend entries separately.
that was rhetorical.. I mean most people use pyplot and every intro matplotlib tutorial I’ve read uses it. The OO interface is the way to go though (or a better plotting package altogether)
34
u/mexiKobe Aug 05 '19
matplotlib’s decision to include MATLAB-like state machine plotting was really stupid. It used to be extremely confusing and I would just write to file and use GNUplot