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

VIS: don't modify matplotlib units registry globally #18720

Closed
jorisvandenbossche opened this issue Dec 11, 2017 · 10 comments · Fixed by #28722
Closed

VIS: don't modify matplotlib units registry globally #18720

jorisvandenbossche opened this issue Dec 11, 2017 · 10 comments · Fixed by #28722
Labels
Milestone

Comments

@jorisvandenbossche
Copy link
Member

Possible follow-up for #18307, see comment there: #18307 (comment) and #18307 (comment) for the details.

Idea would be to only register our converters when we are plotting ourselves, so people plotting directly with matplotlib (plt.plot(..) or ax.plot(..) don't use our converters by default (they can still register them manually with the option).

@TomAugspurger
Copy link
Contributor

Pushing to 0.24.

@jreback
Copy link
Contributor

jreback commented Dec 2, 2018

@TomAugspurger is this doable with the latest mpl release?

@TomAugspurger
Copy link
Contributor

I'm not sure. I don't think it's a blocker for 0.24.0 though.

@TomAugspurger TomAugspurger modified the milestones: 0.24.0, 0.24.1, 0.25.0 Dec 18, 2018
@TomAugspurger
Copy link
Contributor

Pushing to 0.25

@jorisvandenbossche
Copy link
Member Author

Leaving for after 0.25? (1.0)

@jorisvandenbossche jorisvandenbossche modified the milestones: 0.25.0, 1.0 Jun 30, 2019
@TomAugspurger
Copy link
Contributor

TomAugspurger commented Jun 30, 2019 via email

@jorisvandenbossche
Copy link
Member Author

Anyway, given that is a quite annoying change (if you are relying on it), I don't think it hurts to wait a bit longer.

@TomAugspurger
Copy link
Contributor

Can we do this for 1.0? Right now matplotlib is ~25% of our import time(?), and this is the only thing requiring a non-lazy import.

@jorisvandenbossche
Copy link
Member Author

Yes, I think we should try do it for 1.0. We have been raising the deprecation warning for some time now.

@TomAugspurger
Copy link
Contributor

TomAugspurger commented Sep 20, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants