Closed znicholls closed 4 years ago
@gidden and @danielhuppmann maybe one for you as the plotting/packaging experts?
Unfortunately, some features of the plotting library use matplotlib internals, so just removing the pin won't work, see related issues #266, #281, #296, #327.
@gidden, any chance that you look into this?
I agree with the comments that we should allow builds against the latest MPL. I can try to get to that, but am not sure exactly when it would happen.
My suggestion is that we would do the following:
Thoughts?
On Mon, May 11, 2020 at 7:33 AM Daniel Huppmann notifications@github.com wrote:
Unfortunately, some features of the plotting library use matplotlib internals, so just removing the pin won't work, see related issues #266 https://github.com/IAMconsortium/pyam/issues/266, #281 https://github.com/IAMconsortium/pyam/issues/281, #296 https://github.com/IAMconsortium/pyam/issues/296, #327 https://github.com/IAMconsortium/pyam/issues/327.
@gidden https://github.com/gidden, any chance that you look into this?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/IAMconsortium/pyam/issues/374#issuecomment-626479254, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKUAEJPSHIWDOLK6HIBWV3RQ6EZHANCNFSM4M5OBVRQ .
Not sure if I fully get this suggestion - wouldn't that mean that using a "standard-install" to do plots would fail (raise errors)? Don't think that this is a decent user experience...
Matplotlib 3.0.2 was released before matplotlib were packaging Python 3.8 wheels. As a result, it's not trivial to pip install pyam in a Python 3.8 environment. Is it possible to remove this matplotlib pinning and hence support (one-line installs with) Python 3.8?