wq / itertable

⇔ IterTable is a Pythonic API for iterating through tabular data formats, including CSV, XLSX, XML, and JSON.

IterTable is a Pythonic API for iterating through tabular data formats, including CSV, XLSX, XML, and JSON.

from itertable import load_file

for row in load_file("example.xlsx"):
    print(row.date, row.name)

Documentation

Installation

API
CLI • GIS

Extending IterTable
BaseIter • Loaders • Parsers • Mappers

itertable's Issues

csv parser fails on empty file with unhelpful error

as_dataframe()

Would be quite handy to have a built-in option to turn an IO into a Pandas Dataframe.

lxml dependency makes pip install a hassle

py3k

Update to Python 3.X. Will probably just do a full (breaking) switch depending on usage.

Unable to override field_names on CsvNetIO

For .csv files without a header row, I should be able to override the field_names property, but the values are still being read from the .csv instead of the field_names.

command line conversion tool

Implement a command line tool that can convert CSV to Excel or any IO class to csv, etc. Would want it to be pipeable. Something like this:

• wq convert input.csv output.xls
• wq convert mylib.MyCustomIO wq.io.CsvFileIO
• wq cat mylib.MyCustomIO my-io-kwarg=123 > out.csv

use fiona for gis datasets

Replace gis/gdal's dependency on GeoDjango wrapper with Fiona, which includes read-write support.

support pandas-style csv

i.e. port wq/pandas.js to wq.io.

Import data source duplicate field name

Some of the fields in some of my CSV files start with symbols such as $, %, #; and when the data is cleaned then the symbols are removed automatically and I end up with duplicate fields.

Is there a way to override cleaning the column names before mapping starts?

use requests for http

rest api client

Extend JsonNetIO to create a full-featured REST API client (including POST/PUT, etc.). Default implementation should support wq.db-powered REST services and potentially other APIs.

remove python 2 compat

In particular, the unicodecsv detection leads to unexpected behavior changes when working with wq and django-data-wizard/itertable in the same project.