Closed PaleoLipidRR closed 1 year ago
This looks like a dependency issue: proplot 0.9.7 requires matplotlib < 3.5. Not sure how you got incompatible versions -- when I conda install proplot
and pip install proplot
in an empty environment I get matplotlib 3.4.3 (see below). Anyway pip install matplotlib==3.4.3
or conda install -c conda-forge matplotlib=3.4.3
should fix the issue.
$ pip install proplot
Collecting proplot
Using cached proplot-0.9.7-py3-none-any.whl (8.0 MB)
Collecting matplotlib<3.5.0,>=3.3.0
Using cached matplotlib-3.4.3-cp310-cp310-macosx_10_9_x86_64.whl
Requirement already satisfied: numpy>=1.16 in /Users/ldavis/mambaforge/envs/proplot-tmp/lib/python3.10/site-packages (from matplotlib<3.5.0,>=3.3.0->proplot) (1.24.2)
Requirement already satisfied: python-dateutil>=2.7 in /Users/ldavis/mambaforge/envs/proplot-tmp/lib/python3.10/site-packages (from matplotlib<3.5.0,>=3.3.0->proplot) (2.8.2)
Collecting kiwisolver>=1.0.1
Downloading kiwisolver-1.4.4-cp310-cp310-macosx_10_9_x86_64.whl (65 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 65.5/65.5 kB 2.6 MB/s eta 0:00:00
Collecting cycler>=0.10
Using cached cycler-0.11.0-py3-none-any.whl (6.4 kB)
Collecting pyparsing>=2.2.1
Using cached pyparsing-3.0.9-py3-none-any.whl (98 kB)
Collecting pillow>=6.2.0
Downloading Pillow-9.5.0-cp310-cp310-macosx_10_10_x86_64.whl (3.4 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 3.4/3.4 MB 21.5 MB/s eta 0:00:00
Requirement already satisfied: six>=1.5 in /Users/ldavis/mambaforge/envs/proplot-tmp/lib/python3.10/site-packages (from python-dateutil>=2.7->matplotlib<3.5.0,>=3.3.0->proplot) (1.16.0)
Installing collected packages: pyparsing, pillow, kiwisolver, cycler, matplotlib, proplot
Successfully installed cycler-0.11.0 kiwisolver-1.4.4 matplotlib-3.4.3 pillow-9.5.0 proplot-0.9.7 pyparsing-3.0.9
This looks like a dependency issue: proplot 0.9.7 requires matplotlib < 3.5. Not sure how you got incompatible versions -- when I
conda install proplot
andpip install proplot
in an empty environment I get matplotlib 3.4.3 (see below). Anywaypip install matplotlib==3.4.3
orconda install -c conda-forge matplotlib=3.4.3
should fix the issue.$ pip install proplot Collecting proplot Using cached proplot-0.9.7-py3-none-any.whl (8.0 MB) Collecting matplotlib<3.5.0,>=3.3.0 Using cached matplotlib-3.4.3-cp310-cp310-macosx_10_9_x86_64.whl Requirement already satisfied: numpy>=1.16 in /Users/ldavis/mambaforge/envs/proplot-tmp/lib/python3.10/site-packages (from matplotlib<3.5.0,>=3.3.0->proplot) (1.24.2) Requirement already satisfied: python-dateutil>=2.7 in /Users/ldavis/mambaforge/envs/proplot-tmp/lib/python3.10/site-packages (from matplotlib<3.5.0,>=3.3.0->proplot) (2.8.2) Collecting kiwisolver>=1.0.1 Downloading kiwisolver-1.4.4-cp310-cp310-macosx_10_9_x86_64.whl (65 kB) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 65.5/65.5 kB 2.6 MB/s eta 0:00:00 Collecting cycler>=0.10 Using cached cycler-0.11.0-py3-none-any.whl (6.4 kB) Collecting pyparsing>=2.2.1 Using cached pyparsing-3.0.9-py3-none-any.whl (98 kB) Collecting pillow>=6.2.0 Downloading Pillow-9.5.0-cp310-cp310-macosx_10_10_x86_64.whl (3.4 MB) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 3.4/3.4 MB 21.5 MB/s eta 0:00:00 Requirement already satisfied: six>=1.5 in /Users/ldavis/mambaforge/envs/proplot-tmp/lib/python3.10/site-packages (from python-dateutil>=2.7->matplotlib<3.5.0,>=3.3.0->proplot) (1.16.0) Installing collected packages: pyparsing, pillow, kiwisolver, cycler, matplotlib, proplot Successfully installed cycler-0.11.0 kiwisolver-1.4.4 matplotlib-3.4.3 pillow-9.5.0 proplot-0.9.7 pyparsing-3.0.9
Thank you! I created a new environment and do "conda install" with "conda-forge" as my default channel. I am not sure why my matplotlib got installed with the incompatible version. Anyway, thank you so much!
Description
I just recently experience this issue when Proplot (v.0.9.7) started giving errors if I don't specify "share=False" in my first line
fig, axs = plot.subplots()
It's okay if I only plot one subplot.
I run this on .ipynb on VS Studio.
Error Message
Equivalent steps in matplotlib
Please try to make sure this bug is related to a proplot-specific feature. If you're not sure, try to replicate it with the native matplotlib API. Matplotlib bugs belong on the matplotlib github page.