Skip to content

ENH: Make ExcelWriter more easily pluggable #4745

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

Closed
jtratner opened this issue Sep 4, 2013 · 0 comments · Fixed by #4750
Closed

ENH: Make ExcelWriter more easily pluggable #4745

jtratner opened this issue Sep 4, 2013 · 0 comments · Fixed by #4750
Milestone

Comments

@jtratner
Copy link
Contributor

jtratner commented Sep 4, 2013

Basically, make a clear interface for ExcelWriter and allow others to plug into it. Unfortunately, it looks like we're stuck with using ExcelWriter directly as a class, so might take a bit more complexity to stick this in (i.e., a metaclass). If we can convert it to a function instead, can make a lot less magic. Check out this branch if you want to see what I'm talking about.

We'd end up with a separate config option for each extension (io.excel.xlsx.writer, io.excel.xls.writer, io.excel.xlsm.writer) (can't do the reverse because io.excel.writer.xls would match all the different filetypes).

Client code then just has to implement save and write_cells and define supported_extensions and register their their class with register_engine in pandas/io/excel, then it's easily available under to_excel as an engine parameter.

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

Successfully merging a pull request may close this issue.

1 participant