-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Planning for pytplot 2.0 #159
Comments
I'm 100% for this. Me and at least two of my colleagues have spent a good amount of hours diagnosing QT-related errors caused by the current backend. QT stuff also killed PyHC's Gallery page (broke the CI deployment) and prevented us from deploying updates. In another case, a project I know about had to drop pySPEDAS because its PyTplot dependency was breaking things. Matplotlib is the Python standard for plotting things anyway so it makes sense to use it. And it's a big plus to gain compatibility with new platforms, namely notebooks running in browsers, because the pyqtgraph stuff won't be trying to open plots in separate windows. |
Thanks, Shawn! I came across a book this morning that really showcases how powerful matplotlib is: |
I'm creating this issue to start the discussion of moving to pytplot 2.0!
TLDR:
For those of you unaware, I've been developing a version of pytplot that uses matplotlib to generate the figures instead of pyqtgraph; the development has been occuring under the 'matplotlib-backend' branch:
https://github.com/MAVENSDC/PyTplot/tree/matplotlib-backend
There's a jupyter notebook with examples of using this backend at:
https://github.com/MAVENSDC/PyTplot/blob/matplotlib-backend/docs/PyTplot%20examples%20with%20matplotlib.ipynb
For pytplot 2.0, I suggest that we make this backend the default, and deprecate the current Qt backend. I also think we should make this release ASAP.
Why?
I'm sure most of you have encountered some of the recent problems with pyqtgraph; this update will fix all of those issues and introduce several new features.
Bugs this fixes:
New features:
The text was updated successfully, but these errors were encountered: