PyQtGraph VS tools

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/

Ah, I agree, Matplotlib is for publication, so slow and pretty. For fast, I use pyqtgraph, which can do that 10 million point plot interaction. And since it's QT, it integrates seamlessly into QT applications.

This violates the "One Tool" constraint that OP requested, but the Standard Ebooks tool chain is available on Github for anyone interested: https://github.com/standardebooks/tools

The code is GPL-3 and the templates are CC0: https://github.com/standardebooks/tools/blob/master/LICENSE....

Feel free to ask on the mailing list if you have any questions, more likely to be picked up there than in a random HN thread :)

I'll give a shoutout to some other excellent software.

The first is the "Standard Ebooks"[1] toolset, which is a suite of Python scripts to create, process, and build ebooks in all common formats. The results on the Standard Ebooks site speak for themselves. They're impeccable in every way, and far better than many big name, commercially produced efforts.

GitHub: https://github.com/standardebooks/tools

This question comes up a lot. The source to our production pipeline is GPLed and freely available,[1] but the biggest part of why we produce good work is that we have a high quality manual of style.[2] Unfortunately, that second part is very specific to English, and that’s the difficult part to replicate for other languages.

[1] https://github.com/standardebooks/tools/

[2] https://standardebooks.org/manual/