Write to StringIO object using Pandas Excelwriter?

后端 未结 3 1842
夕颜
夕颜 2020-11-30 10:37

I can pass a StringIO object to pd.to_csv() just fine:

io = StringIO.StringIO()
pd.DataFrame().to_csv(io)

But when using the excel writer,

相关标签:
3条回答
  • 2020-11-30 10:49

    Glancing at the pandas.io.excel source looks like it shouldn't be too much of a problem if you don't mind using xlwt as your writer. The other engines may not be all that difficult either but xlwt jumps out as easy since its save method takes a stream or a filepath.

    You need to initially pass in a filename just to make pandas happy as it checks the filename extension against the engine to make sure it's a supported format. But in the case of the xlwt engine, it just stuffs the filename into the object's path attribute and then uses it in the save method. If you change the path attribute to your stream, it'll happily save to that stream when you call the save method.

    Here's an example:

    import pandas as pd
    import StringIO
    import base64
    
    df = pd.DataFrame.from_csv('http://moz.com/top500/domains/csv')
    xlwt_writer = pd.io.excel.get_writer('xlwt')
    my_writer = xlwt_writer('whatever.xls')  #make pandas happy 
    xl_out = StringIO.StringIO()
    my_writer.path = xl_out  
    df.to_excel(my_writer)
    my_writer.save()
    print base64.b64encode(xl_out.getvalue())
    

    That's the quick, easy and slightly dirty way to do it. BTW... a cleaner way to do it is to subclass ExcelWriter (or one of it's existing subclasses, e.g. _XlwtWriter) -- but honestly there's so little involved in updating the path attribute, I voted to show you the easy way rather than go the slightly longer route.

    0 讨论(0)
  • 2020-11-30 10:54

    For those not using xlsxwriter as their engine= for to_excel here is a solution to use openpyxl in memory:

    in_memory_file = StringIO.StringIO()
    xlw = pd.ExcelWriter('temp.xlsx', engine='openpyxl')
    # ... do many .to_excel() thingies
    xlw.book.save(in_memory_file)
    # if you want to read it or stream to a client, don't forget this
    in_memory_file.seek(0)
    

    explanation: the ExcelWriter wrapper class exposes the engines individual workbook through the .book property. For openpyxl you can then use the Workbook.save method as usual!

    0 讨论(0)
  • 2020-11-30 10:56

    Pandas expects a filename path to the ExcelWriter constructors although each of the writer engines support StringIO. Perhaps that should be raised as a bug/feature request in Pandas.

    In the meantime here is a workaround example using the Pandas xlsxwriter engine:

    import pandas as pd
    import StringIO
    
    io = StringIO.StringIO()
    
    # Use a temp filename to keep pandas happy.
    writer = pd.ExcelWriter('temp.xlsx', engine='xlsxwriter')
    
    # Set the filename/file handle in the xlsxwriter.workbook object.
    writer.book.filename = io
    
    # Write the data frame to the StringIO object.
    pd.DataFrame().to_excel(writer, sheet_name='Sheet1')
    writer.save()
    xlsx_data = io.getvalue()
    

    Update: As of Pandas 0.17 it is now possible to do this more directly:

    # Note, Python 2 example. For Python 3 use: output = io.BytesIO().
    output = StringIO.StringIO()
    
    # Use the StringIO object as the filehandle.
    writer = pd.ExcelWriter(output, engine='xlsxwriter')
    

    See also Saving the Dataframe output to a string in the XlsxWriter docs.

    0 讨论(0)
提交回复
热议问题