libxlsxwpy - Let you focus on data, instead of file formats

Support the project

If your company has embedded pyexcel and its components into a revenue generating product, please support me on github, patreon or bounty source to maintain the project and develop it further.

If you are an individual, you are welcome to support me too and for however long you feel like. As my backer, you will receive early access to pyexcel related contents.

And your issues will get prioritized if you would like to become my patreon as pyexcel pro user.

With your financial support, I will be able to invest a little bit more time in coding, documentation and writing interesting posts.

Known constraints

Fonts, colors and charts are not supported.

Introduction

libxlsxwpy is a plain python wrapper for libxlsxwriter, a c library. And it supports: write string, boolean, datetime and number.

Installation

First of all, please install libxlsxwriter.

You can clone it and install it:

$ git clone http://github.com/pyexcel/libxlsxwpy.git
$ cd libxlsxwpy
$ python setup.py build
$ python setup.py install

Usage

Here is the python code for the equivalent C code:

>>> from libxlsxwpy import Book
>>> book = Book()
>>> book.open("myexcel.xlsx")
True
>>> sheet = book.add_worksheet()
>>> sheet.write_string(0, 0, "Hello me!")
True
>>> book.close()
True

.. testcode::
   :hide:

    >>> import os
    >>> os.unlink("myexcel.xlsx")

Development guide

Development steps for code changes

1. git clone https://github.com/pyexcel/libxlsxwpy.git
2. cd libxlsxwpy

Upgrade your setup tools and pip. They are needed for development and testing only:

1. pip install --upgrade setuptools pip

Then install relevant development requirements:

1. pip install -r rnd_requirements.txt # if such a file exists
2. pip install -r requirements.txt
3. pip install -r tests/requirements.txt

Once you have finished your changes, please provide test case(s), relevant documentation and update CHANGELOG.rst.

How to test your contribution

Although nose and doctest are both used in code testing, it is adviable that unit tests are put in tests. doctest is incorporated only to make sure the code examples in documentation remain valid across different development releases.

On Linux/Unix systems, please launch your tests like this:

$ make

On Windows systems, please issue this command:

> test.bat

Before you commit

Please run:

$ make format

so as to beautify your code otherwise travis-ci may fail your unit test.

License

New BSD License