Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Should we override the matplotlib color shorthands?
See original GitHub issueMatplotlib lets you specify colors like "b" for blue, "r" for red, etc. which is nice. But, those colors are mapped to the corners of RGB space, which, bleh.
This is additionally problematic as some functions (like plt.scatter) hardcode these values as default.
It occurs to me that seaborn could override this by messing with the values in the mpl.colors.ColorConverter.colors dictionary. But that might be too much manipulation?
Opening this issue for discussion.
Issue Analytics
- State:
- Created 9 years ago
- Comments:27 (19 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
For what it’s worth, I think this would be fine (and appreciated). Users who are concerned preserving the exact original styling of their matplotlib figures won’t be using
import seabornanyways.Thanks, I see the fix in 0.5.1, sorry to muddle the current thread.