| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
Thank you for opening your first PR into Matplotlib!
If you have not heard from us in a while, please feel free to ping @matplotlib/developers or anyone who has commented on the PR. Most of our reviewers are volunteers and sometimes things fall through the cracks.
You can also join us on gitter for real-time discussion.
For details on testing, writing docs, and our review process, please see the developer guide
We strive to be a welcoming and open project. Please follow our Code of Conduct.
Sorry, something went wrong.
There was a problem hiding this comment.
Looks good. not sure, but should this be in test_backend_tools.py?
Sorry, something went wrong.
I put the test in test_backend_tk.py as this was a bug related only to TkAgg AFAIK. The actual bug fix is in _backends/backend_tk.py. |
Sorry, something went wrong.
Thats probably fine, but is the same bug present in other backends? |
Sorry, something went wrong.
As the bug stems from the backend_tk.py file It would seem the bug would only affect this backend. Additionally, I just tested with qtagg and PyQt6 and there is no bug on the main branch. |
Sorry, something went wrong.
|
Thats great - however, does the test apply to the other backends? If so, perhaps better to put somewhere that all the backends get tested to increase our test coverage? BTW, I haven't checked all this, so feel free to tell me the test is definitely only useful for Tk and I'm happy to approve - we can always generalize the test later if you are not correct. |
Sorry, something went wrong.
|
Indeed, this test could be applied to any backend! You are right that it would be more useful if I can parametrize the test for any backend. Although I am not familiar with the whole set of matplotlib unittests. Do you know if there are tests that parametrize over backends so that I can generalize the one I introduce here? Thanks |
Sorry, something went wrong.
I used the parametrization defined in test_backends_interactive.py in order to get environments with different backends and run them in a subprocess helper function. The parametrization now gives ~13 tests for different configuration. I tested with pyqt6, pyside6 and pycairo installed in my environment and it seems to work. I couldn't make it work with pyqt5 and other pysides as I had trouble installing these packages. |
Sorry, something went wrong.
|
Oh it seems there is a very similar bug in the wx backend seen on appveyor. I could reproduce it locally and fixed it. I'll push the fix. |
Sorry, something went wrong.
|
Sorry for the conflicting informations, but I think this test should rather go into test_backends_interactive.py::_test_interactive_impl. This is because interactive tests are very, very slow to start up (as they need to be run into their own subprocess) so it is better to try and minimize the number of tests and do more in a single test. Probably we should better document this at the top of test_backends_interactive.py... |
Sorry, something went wrong.
Sure I'll move it there |
Sorry, something went wrong.
There was a problem hiding this comment.
Modulo sorting out the extra try/except added in the test.
Sorry, something went wrong.
|
Thank you for your work on this @fgoudreault and congratulations on your first merged Matplotlib PR 🎉 I hope we hear from you again! |
Sorry, something went wrong.
The pleasure is mine! Thanks to all for your time! |
Sorry, something went wrong.
…174-on-v3.7.x Backport PR #25174 on branch v3.7.x (Accept LA icons for the toolbar)
| Back | FazBrowse Home | New Git URL |
PR Summary
Fixes #25164 by converting a PIL icon image to RGBA when loading it. Also created unittest to check the bug in the future.
PR Checklist
Documentation and Tests
Release Notes