https://github.com/pyexcel/pyexcel-odsw
Writer an ods using loxun XMLWriter with constant memory
https://github.com/pyexcel/pyexcel-odsw
Last synced: about 1 year ago
JSON representation
Writer an ods using loxun XMLWriter with constant memory
- Host: GitHub
- URL: https://github.com/pyexcel/pyexcel-odsw
- Owner: pyexcel
- License: other
- Created: 2018-08-04T23:07:51.000Z (over 7 years ago)
- Default Branch: master
- Last Pushed: 2020-10-18T13:55:31.000Z (over 5 years ago)
- Last Synced: 2025-01-11T05:19:21.750Z (over 1 year ago)
- Language: Python
- Size: 39.1 KB
- Stars: 1
- Watchers: 3
- Forks: 1
- Open Issues: 1
-
Metadata Files:
- Readme: README.rst
- Changelog: CHANGELOG.rst
- Funding: .github/FUNDING.yml
- License: LICENSE
Awesome Lists containing this project
README
================================================================================
pyexcel-odsw - Let you focus on data, instead of file formats
================================================================================
.. image:: https://raw.githubusercontent.com/pyexcel/pyexcel.github.io/master/images/patreon.png
:target: https://www.patreon.com/chfw
.. image:: https://raw.githubusercontent.com/pyexcel/pyexcel-mobans/master/images/awesome-badge.svg
:target: https://awesome-python.com/#specific-formats-processing
.. image:: https://travis-ci.org/pyexcel/pyexcel-odsw.svg?branch=master
:target: http://travis-ci.org/pyexcel/pyexcel-odsw
.. image:: https://codecov.io/gh/pyexcel/pyexcel-odsw/branch/master/graph/badge.svg
:target: https://codecov.io/gh/pyexcel/pyexcel-odsw
.. image:: https://img.shields.io/gitter/room/gitterHQ/gitter.svg
:target: https://gitter.im/pyexcel/Lobby
.. image:: https://img.shields.io/static/v1?label=continuous%20templating&message=%E6%A8%A1%E7%89%88%E6%9B%B4%E6%96%B0&color=blue&style=flat-square
:target: https://moban.readthedocs.io/en/latest/#at-scale-continous-templating-for-open-source-projects
.. image:: https://img.shields.io/static/v1?label=coding%20style&message=black&color=black&style=flat-square
:target: https://github.com/psf/black
.. image:: https://readthedocs.org/projects/pyexcel-odsw/badge/?version=latest
:target: http://pyexcel-odsw.readthedocs.org/en/latest/
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.
Introduction
================================================================================
**pyexcel-odsw** does write an ods file using constant memory.
Installation
================================================================================
You can get it:
.. code-block:: bash
$ git clone https://github.com/pyexcel/pyexcel-odsw.git
$ cd pyexcel-odsw
$ python setup.py install
Development guide
================================================================================
Development steps for code changes
#. git clone https://github.com/pyexcel/pyexcel-odsw.git
#. cd pyexcel-odsw
Upgrade your setup tools and pip. They are needed for development and testing only:
#. pip install --upgrade setuptools pip
Then install relevant development requirements:
#. pip install -r rnd_requirements.txt # if such a file exists
#. pip install -r requirements.txt
#. pip install -r tests/requirements.txt
Once you have finished your changes, please provide test case(s), relevant documentation
and update CHANGELOG.rst.
.. note::
As to rnd_requirements.txt, usually, it is created when a dependent
library is not released. Once the dependecy is installed
(will be released), the future
version of the dependency in the requirements.txt will be valid.
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