Skip to content
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

Drop support for Matplotlib < 1.5.1 and NumPy < 1.10 #1041

Merged
merged 3 commits into from
Apr 26, 2018

Conversation

QuLogic
Copy link
Member

@QuLogic QuLogic commented Feb 28, 2018

We don't even test with 1.3.0 any more, and 1.4.3 is 3 years old now. Anything older than that is not even easy to install with conda either. I chose 1.5 because it was the last major version to use the old style, but we could go with 2.0 instead.

Not sure if conda will like the package set specified right now; we'll see how well the old build works.

@QuLogic QuLogic added this to the 0.17 milestone Feb 28, 2018
@QuLogic QuLogic force-pushed the mpl-bump branch 2 times, most recently from 64d3a6f to d2ce4ff Compare February 28, 2018 02:55
@QuLogic
Copy link
Member Author

QuLogic commented Feb 28, 2018

So conda only has Matplotlib 1.5.0 linked against NumPy 1.10; I had to bump that minimum version as well. It was released around the same time, so hopefully that's not a problem.

@QuLogic QuLogic changed the title Drop support for Matplotlib < 1.5. Drop support for Matplotlib < 1.5 and NumPy < 1.10 Feb 28, 2018
@QuLogic QuLogic force-pushed the mpl-bump branch 4 times, most recently from 01c2170 to 99060d5 Compare February 28, 2018 05:03
We don't even test with 1.3.0 any more, and 1.4.3 is 3 years old now.
Anything older than that is not even easy to install with conda either.
This was released around the same time as Matplotlib 1.5.0.
@QuLogic
Copy link
Member Author

QuLogic commented Feb 28, 2018

So I just remembered that conda packages mpl 1.5.0 in a broken way, so had to bump to 1.5.1. It came out only a few months after though.

@QuLogic QuLogic changed the title Drop support for Matplotlib < 1.5 and NumPy < 1.10 Drop support for Matplotlib < 1.5.1 and NumPy < 1.10 Feb 28, 2018
@SciTools SciTools deleted a comment from stickler-ci Mar 3, 2018
Copy link
Member

@pelson pelson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great. very pleasing to see the simplification this makes! 👍

I have one little question, but otherwise, LGTM

except AttributeError:
matplotlib.axes._subplot_classes[GeoAxes] = GeoAxesSubplot
GeoAxesSubplot = matplotlib.axes.subplot_class_factory(GeoAxes)
GeoAxesSubplot.__module__ = GeoAxes.__module__
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did something change?

Copy link
Member Author

@QuLogic QuLogic Apr 26, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See the comment above; this ensures that we get cartopy.mpl.geoaxes.GeoAxesSubplot instead of some matplotlib path (since by using the subplot_class_factory, it's created there.) Also, see last commit's description.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wrote that comment, but didn't write the __module__ part 😃 - so was getting some clarification.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, well, not using the private API necessitated a small change in how the module path was fixed.

@pelson
Copy link
Member

pelson commented Apr 26, 2018

Excellent, thanks @QuLogic!

@QuLogic QuLogic deleted the mpl-bump branch April 26, 2018 06:57
tacaswell added a commit to tacaswell/matplotlib that referenced this pull request Sep 15, 2018
closes matplotlib#11966

The issue has also been fixed on the cartopy
side (SciTools/cartopy#1041) but has not been
released yet.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants