-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
[Bug]: mplsetup.cfg parsing issue #21660
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
Comments
due to the way we now use the matplotlibrc shipped as part of the package the expected outcome is
however, as of the last few minor releases of Matplotlib we will auto-detect which backend to use based on what is available so if you are on OSX, it will automatically default to using I'm working on the (2 character) PR to fix this... |
Thanks! I'm working on Spack's matplotlib package and we would like to force an installation to use a particular backend. In prior releases, we could simply set this in P.S. If any matplotlib developers would like to help maintain Spack's build recipe for matplotlib just let me know |
The I assume that spack has a way of including patches? The change in #21662 should be sufficient to un-stick you. |
Okay, so if I understand correctly: For older versions of matplotlib (3.4 and older), the For newer versions of matplotlib (3.5 and newer), the Is this understanding correct? Yes, Spack has a way to include patches, I'll test and include yours. |
@adamjstewart Yes that is correct. |
It's still possible to hit this issue if |
Bug summary
mplsetup.cfg
isn't being parsed correctly, leading to an invalidmatplotlibrc
being installed.Code for reproduction
Actual outcome
The
matplotlibrc
that gets installed contains:Expected outcome
The
matplotlibrc
should instead contain:Additional information
When I try to import this installation, I see:
Operating system
macOS
Matplotlib Version
3.5.0
Matplotlib Backend
macosx
Python version
3.8.12
Jupyter version
N/A
Installation
from source (.tar.gz)
The text was updated successfully, but these errors were encountered: