PyQtGraph VS matplotlib

Very interesting and promising package.

I especially like that there is a PyQt interface which might provide an alternative to another great package: pyqtgraph[0].

[0] https://github.com/pyqtgraph/pyqtgraph

PyQtGraph - Interactive and realtime 2D/3D/Image plotting and science/engineering widgets.

Image, 3D, or data visualization applications using OpenCV and the SciPy ecosystem. The Graphics View Framework can display an image and let the user interact with it, and the Python ecosystem is very rich for image processing, data analysis, and visualization. For example, LabelMe for image labeling, PyQtGraph for scientific graphics, or custom QWidget integration in Maya.

I don't think that's related to your error though - from the backtrace, it looks like the plotWidget has plotItem attribute that's somehow been assiged to itself (or maybe some other PlotWidget) , so is just endlessly recursing as it tries to proxy the same attribute lookup (presumably 'clear') to itself. Looking at the source, the plotitem is either created as a new PlotItem() object if not provided, or passed in to the constructor, so I'd check how this gets initialised - eg. does this get set as a property in your .ui file? Are you setting it to the widget itself somehow?

I did something like this recently but I used pyqtgraph: https://www.pyqtgraph.org/

As is the case with most Python libraries, it is open-source and free-to-use, making it easily accessible by anyone willing to learn machine learning, and it is built upon other open-source libraries within Python, like SciPy for advanced scientific operations, NumPy for efficient numerical computations, Matplotlib for data visualization, and Cython for increased efficiency and speed, similar to that of C/C++.

The source code for Matplotlib is located at this github repository https://github.com/matplotlib/matplotlib

Difficult to draw conclusions with no code here.

An interesting thing they didn't mention is that Matplotlib's point-in-path code is actually already in C. So this isn't really a case of Rust being X times faster than Python, it's X times faster than some other C algorithm. That's probably why X is only ~4 (they don't actually give a single-thread comparison), instead of ~50.

https://github.com/matplotlib/matplotlib/blob/cb487f3c077c93...

I expect the Rust code is faster because that code is waaaaay more complicated than what they probably need (https://stackoverflow.com/q/11716268/265521) - e.g. it handles stroke widths.

IMO this result is not very interesting.

Github: https://github.com/matplotlib/matplotlib

as suggested here.

Tool: Matplotlib Pyplot

The issue was described here: https://github.com/matplotlib/matplotlib/issues/8409, but the "solution" was just "this is fixed" which was not helpful to me.

Matplotlib: Matplotlib is a 2D plotting library that allows you to create visualizations of your data. It's a powerful tool for data analysis, but the syntax can be complex and the customization options can be overwhelming. GitHub - https://github.com/matplotlib/matplotlib