Skip to main content

read Microsoft Excel tm xlsb file

Project description

https://raw.githubusercontent.com/pyexcel/pyexcel.github.io/master/images/patreon.png https://api.bountysource.com/badge/team?team_id=288537 https://travis-ci.org/pyexcel/pyexcel-xlsbr.svg?branch=master https://codecov.io/gh/pyexcel/pyexcel-xlsbr/branch/master/graph/badge.svg https://img.shields.io/gitter/room/gitterHQ/gitter.svg https://readthedocs.org/projects/pyexcel-xlsbr/badge/?version=latest

Support the project

If your company has embedded pyexcel and its components into a revenue generating product, please support me on 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-xlsbr does read Microsoft Excel tm xlsb file. So far, it can read data out but cannot recognize date time format from float datat type.

Installation

You can install pyexcel-xlsbr via pip:

$ pip install pyexcel-xlsbr

or clone it and install it:

$ git clone https://github.com/pyexcel/pyexcel-xlsbr.git
$ cd pyexcel-xlsbr
$ python setup.py install

Development guide

Development steps for code changes

  1. git clone https://github.com/pyexcel/pyexcel-xlsbr.git

  2. cd pyexcel-xlsbr

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

How to update test environment and update documentation

Additional steps are required:

  1. pip install moban

  2. git clone https://github.com/moremoban/setupmobans.git # generic setup

  3. git clone https://github.com/pyexcel/pyexcel-commons.git commons

  4. make your changes in .moban.d directory, then issue command moban

What is pyexcel-commons

Many information that are shared across pyexcel projects, such as: this developer guide, license info, etc. are stored in pyexcel-commons project.

What is .moban.d

.moban.d stores the specific meta data for the library.

Acceptance criteria

  1. Has Test cases written

  2. Has all code lines tested

  3. Passes all Travis CI builds

  4. Has fair amount of documentation if your change is complex

  5. run ‘make format’ so as to confirm the pyexcel organisation’s coding style

  6. Please update CHANGELOG.rst

  7. Please add yourself to CONTRIBUTORS.rst

  8. Agree on NEW BSD License for your contribution

License

New BSD License

Change log

0.5.0-rc1 - 14.03.2019

first release

  1. read data out from xlsb format but to pyexcel-io’s standard

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

pyexcel-xlsbr-0.5.0rc1.tar.gz (15.6 kB view hashes)

Uploaded Source

Built Distribution

pyexcel_xlsbr-0.5.0rc1-py2.py3-none-any.whl (5.8 kB view hashes)

Uploaded Python 2 Python 3

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page