Closed GilChrist19 closed 3 months ago
Hi, I’m not sure I understand the question here. If you are setting up an environment with an archaic version of seaborn, you should require a suitably old and compatible version of matplotlib as well.
Hello Michael,
That's true - totally agree.
The problem is that there's no rule for the environment/dependency solver to enforce that, something like this line in the current versions. Therefore Mamba builds the environment with the current version of matplotlib
even though it's incompatible.
Not sure if it's possible to update "matplotlib>=3.4,!=3.6.1",
to something like "matplotlib>=3.4,!=3.6.1,<3.9",
in older versions to ensure matching dependencies upon installation.
~Jared
It’s not possible to retroactively change older versions. It sounds like you are maybe installing a third package that pins an old version of seaborn. I would say that package would have the responsibility to also limit the matplotlib version that it is compatible with, as it is transitively incompatible with 3.9 via seaborn at least.
I am unable to import seaborn when installed to an environment with matplotlib 3.9.x.
Error is:
AttributeError: module 'matplotlib.cm' has no attribute 'register_cmap'
However,
and
both work fine.
I realize an older version of
seaborn
is being installed (0.11 I believe), due to compatibility withstatannotations
, and that's what's struggling with thematplotlib
versions.Is there a way to set the
matplotlib
dependency <3.9 for older versions ofseaborn
, as that's when they updated the internal API.