DOC: Update instructions on pandas converters #9251
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
anntzer
approved these changes
Sep 28, 2017
tacaswell
added a commit
that referenced
this pull request
Sep 29, 2017
DOC: Update instructions on pandas converters
|
Thanks @TomAugspurger ! Backported to v2.1.x as c8c76ad |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Summary
In pandas 0.21 (release in a week or 2), pandas will no longer try to import matplotlib on import, see pandas-dev/pandas#17710. This means pandas' converters won't be automatically registered. I've updated the relevant section of the matplotlib docs.
I opted for brevity, and didn't include a note saying that previous versions of pandas did the automatic registration. If you'd like, I can add one.
And of course, moving these formatters out of pandas is still on my todo list. Maybe someday :)
PR Checklist