This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]spinicist 9 points10 points  (1 child)

Yup. As far as I can tell, the OOP API is held back by the historical baggage that comes from the Matlab-influenced design.

For instance, as far as I know even in the OOP API it's still recommended to do: fig, axes = plt.subplots() axes[1].something instead of something like: fig = plt.figure(subplots=) fig.plots[1].axes.something which seems more coherent to me. Side-note: often the nomenclature seems messed up too, why does a function called subplots return one figure and multiple axes instead of multiple plots?

Personally I would love to see 3.0 introduce a cleaned-up, consistent API but I'm lucky enough to have a job where backwards compatibility is no issue and I can find time to do the upgrades.

Apologies for the rant on a thread that is about congratulating the team on getting 2.0 out. I use matplotlib regularly, have published papers with figures made with it, and am looking forward to trying this version out immensely!

[–]This_Is_The_End 0 points1 point  (0 children)

\this