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.
DOC: Mention styler in the to_excel documentation
See original GitHub issuexref #47525
In our DataFrame.to_excel documentation we don’t have any mention to Styler.to_excel which is very relevant.
Users checking the documentation on how to export a DataFrame to Excel should be aware that they can use the Styler to format the exported file. Personally I’d add the class to See Also, and I’d add a very short example at the end of our examples, with a link to the Styler.to_excel page. I think that would be good for users who may be interested in that feature. But other ideas also welcome.
Issue Analytics
- State:
- Created a year ago
- Comments:11 (9 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
@FrnRmn - you’re definitely on the right track here! The links should work, and for this issue we want to mention
Styler.to_exceland not justStyler.I’m +1 on See Also and even an explicit note on when the Styler should be used (no surprise: adding styles to Excel output), but I don’t think we should have examples of method A in the API docs of method B, even if they are closely related.