Support Python 3.3 and up #239

Closed
petri opened this Issue Dec 1, 2013 · 14 comments

Comments

Projects
None yet
8 participants

petri commented Dec 1, 2013

'nuf said.

👍

ztane commented May 29, 2014

There is a dependence on DBF lib, that is certainly not installable on Python 3, even uses raise AttributeError, message and all other sorts of abominations; should be made optional.

+1 for making it optional. Perhaps someone who uses the dbf module could also post a formal request for Python 3.x support on https://groups.google.com/forum/#!forum/python-dbase, and link to that back here.

sirex commented Jun 1, 2014

+1 for Python 3 support.

bijzz commented Jun 13, 2014

+1 really hinders the workflow if one cant use csvkit in a python 3 environment.

arowla commented Jul 16, 2014

+1

csvkit pooped with python 3.
👍 for this ticket
@onyxfish - do you have any plans for this in the very near future?

@onyxfish onyxfish added a commit that referenced this issue Jul 24, 2014

@onyxfish onyxfish Starting Py3 port. #239. fb05a98
Collaborator

onyxfish commented Jul 26, 2014

I've now got a Python 3.3 and 3.4 version of csvkit passing almost all tests on a branch. (https://github.com/onyxfish/csvkit/tree/py3) Python 2.6 and 2.7 are supported with the same code. This is far and away the most complex Python 2/3 codebase I've architected, so I'd love to have more eyes on it. Please feel free to check it out and take it for a spin.

I did a quick check and poke around. Looks good to me. Because I know you are a huge Zac Efron fan, I will leave you with this for your awesome responsiveness:
Zac Efron

Collaborator

onyxfish commented Jul 26, 2014

Merged in. Still resolving some lingering issues, but will be in the next release.

onyxfish closed this Jul 26, 2014

Collaborator

onyxfish commented Jul 28, 2014

For those who were waiting for this, it has now been released:

http://csvkit.readthedocs.org/en/0.8.0/

YAY!

@onyxfish Nice work!

arowla commented Jul 29, 2014

Thank you, @onyxfish !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment