compat.py.
The code in tablib/formats/_xls.py used xrange in parsing excel spreadsheets.
xrange is not a builtin for Python 3, so I've added
xrange = range
in compat.py and imported it in tablib/formats/_xls.py.
The example was triggering this error:
JSONError: Expecting property name: line 1 column 3 (char 2)
This is because JSON property names should be wrapped in double
quotes.
While at it, I've fixed the typo in "last_name"
Fixing indentation issues (off by one space), which caused problems
with the sphinx rendering of the DBF docstring and otherwise cleaning
up the sphinx docstring.
Squashing two squashes.
Adding DBF support
Adding the DBFpy python package
The DBFpy package provides basic dbf support for python. Still need to
write an interface format file for tablib.
Adding DBF format and imports in compat.py
Adding DBF format to formats.__init__
DBF format had not been committed to formats.__init__, so I’m adding it.
Adding a dbf import test
Adding at test to check whether a DBF can be created properly and
compare it against a regression binary string.
Adding an import_set test (and renaming another)
Adding an import_set test that conforms with the other import_set tests
for other formats. I’m also adding an export_set function.
Fixing system site-packages import
Importing dbfpy from tab lib.packages instead of system site packages.
Fixing a syntaxError in dbfpy/dbfnew.py
Fixing an issue with ending field definitions
DBFPY, when writing a DBF, terminates the field definitions with a
newline character. When importing a DBF from a stream, however, DBFPY
was looking only for the \x0D character rather than the newline. Now
we consider both cases.
Adding a test for dbf format detection
Adding DBF filetype detection tests
Adding tests for YAML, JSON, TSV, CSV using the DBF detection function.
Handling extra exceptions in dbf detection
Adding exception handling for struct.error, an exception that DBFPY
raises when trying to unpack a TSV table. Since it’s not a DBF file,
we know it’s not a DBF and return False.
Fixing an issue with the DBF set exporting test
The DBF set export test needed a bit enabled (probably the writeable
bit?) before the test would match the regression output.
Updating dbf interface
Updating the int/float class/type checking in the dbf format file.
This allows for python2 and python3 compatibility.
Tweaking dbfpy to work with python3
Altering a couple of imports.
Updating dbf tests for binary data compatibility
Making regression strings binary and improving debug messages for dbf
assertion errors.
Improving file handling for python 2 and 3
Updating DBF file handling for both python 2 and 3 in the _dbf
interface.
Adding a (seemingly) functional dbfpy for python3
I’ve made dbfpy python3 compatible! Tests appear to pass.
A significant change was made to the format detection test whereby I
made the input string a binary (bytes) string. If the string is not a
bytes string by the time we try to detect the format, we try to decode
the string as utf-8 (which admittedly might not be the safest thing to
do) and try to decode anyways.
Updating imports for tablib dbf interface
Now importing python2 or python3 versions as appropriate.
Updating dbf package references in compat.py
Cleaning up debugging print statements
Updating stream handling in dbf interface
Factoring the open() call out of the py3 conditional and removing the
temp file before returning the stream value.
Adding dbfpy3 init.py
I had apparently missed the dbfpy3 init file when committing dbfpy3.
Adding dbfpy and dbfpy3 to setup.py's package list
Switching test order of formats
Putting dbf format testing ahead of TSV. In some of my tests with
numeric DBF files, I encountered an issue where the ASCII horizontal
tab character (0x09) would appear in a numeric DBF. Because of the
order of tabular format imports, though, format detection would
recognize it as a TSV and not as a DBF.
Adding my name to AUTHORS.
Adding a DBF property to tab lib core
Documentation includes examples on how to explicitly load a DBF
straight from a file and how to load a DBF from a binary string. Also,
how to write the binary data to a file.
Adding DBF format notes to README
Adding exclamation point to DBF section title
Matching formatting of XLS section
Updating setup.py to match current dev state
Setup.py had been updated since I forked the tablib repo, so I’m
updating setup.py to match its current structure while still
maintaining DBF compatibility.
Fixed callable collumn test
the test was sending a list instead of a function
CORE CONTRIBUTORS
🍰 @iurisilvio
v0.10.0
WHEELS
3.3, 3.4
makefile for WHEELS
v0.10.0 history
ALL
Separate py2 and py3 packages to avoid installation errors. Fix#151
Running travis and tox with python 3.4.
Adding DBF support
Adding the DBFpy python package
The DBFpy package provides basic dbf support for python. Still need to
write an interface format file for tablib.
Adding DBF format and imports in compat.py
Adding DBF format to formats.__init__
DBF format had not been committed to formats.__init__, so I’m adding it.
Adding a dbf import test
Adding at test to check whether a DBF can be created properly and
compare it against a regression binary string.
Adding an import_set test (and renaming another)
Adding an import_set test that conforms with the other import_set tests
for other formats. I’m also adding an export_set function.
Fixing system site-packages import
Importing dbfpy from tab lib.packages instead of system site packages.
Fixing a syntaxError in dbfpy/dbfnew.py
Fixing an issue with ending field definitions
DBFPY, when writing a DBF, terminates the field definitions with a
newline character. When importing a DBF from a stream, however, DBFPY
was looking only for the \x0D character rather than the newline. Now
we consider both cases.
Adding a test for dbf format detection
Adding DBF filetype detection tests
Adding tests for YAML, JSON, TSV, CSV using the DBF detection function.
Handling extra exceptions in dbf detection
Adding exception handling for struct.error, an exception that DBFPY
raises when trying to unpack a TSV table. Since it’s not a DBF file,
we know it’s not a DBF and return False.
Fixing an issue with the DBF set exporting test
The DBF set export test needed a bit enabled (probably the writeable
bit?) before the test would match the regression output.
Updating dbf interface
Updating the int/float class/type checking in the dbf format file.
This allows for python2 and python3 compatibility.
Tweaking dbfpy to work with python3
Altering a couple of imports.
Updating dbf tests for binary data compatibility
Making regression strings binary and improving debug messages for dbf
assertion errors.
Improving file handling for python 2 and 3
Updating DBF file handling for both python 2 and 3 in the _dbf
interface.
Adding a (seemingly) functional dbfpy for python3
I’ve made dbfpy python3 compatible! Tests appear to pass.
A significant change was made to the format detection test whereby I
made the input string a binary (bytes) string. If the string is not a
bytes string by the time we try to detect the format, we try to decode
the string as utf-8 (which admittedly might not be the safest thing to
do) and try to decode anyways.
Updating imports for tablib dbf interface
Now importing python2 or python3 versions as appropriate.
Updating dbf package references in compat.py
Cleaning up debugging print statements
Updating stream handling in dbf interface
Factoring the open() call out of the py3 conditional and removing the
temp file before returning the stream value.
Adding dbfpy3 init.py
I had apparently missed the dbfpy3 init file when committing dbfpy3.
Adding dbfpy and dbfpy3 to setup.py's package list
Switching test order of formats
Putting dbf format testing ahead of TSV. In some of my tests with
numeric DBF files, I encountered an issue where the ASCII horizontal
tab character (0x09) would appear in a numeric DBF. Because of the
order of tabular format imports, though, format detection would
recognize it as a TSV and not as a DBF.
Adding my name to AUTHORS.
Adding a DBF property to tab lib core
Documentation includes examples on how to explicitly load a DBF
straight from a file and how to load a DBF from a binary string. Also,
how to write the binary data to a file.
Adding DBF format notes to README
Adding exclamation point to DBF section title
Matching formatting of XLS section
Updating setup.py to match current dev state
Setup.py had been updated since I forked the tablib repo, so I’m
updating setup.py to match its current structure while still
maintaining DBF compatibility.
Fixed callable collumn test
the test was sending a list instead of a function
CORE CONTRIBUTORS
🍰 @iurisilvio
v0.10.0
WHEELS
3.3, 3.4
makefile for WHEELS
v0.10.0 history
ALL
Separate py2 and py3 packages to avoid installation errors. Fix#151
Running travis and tox with python 3.4.
The old version of unicodecsv incorrectly (according
https://docs.python.org/2/library/csv.html#csv.writer) encoding None
values as the string 'None', instead of the string '' as the python
documentation specifies.
The newest version of unicodecsv has fixed this.
Fixes#121
* Alter `test_unicode_append` so that actual unicode characters outside the ASCII bytestring range are tested.
* Make sure output of `render` in markup.py is unicode
* Add wrapper around output of `export_set` in _html.py so that unicode characters are output.
Rumpu-Jussi
kennethreitz