Python 3 Support

[bemcdonnell]

I've got a first iteration here for Py34 support on Windows. If you guys could check out my branch and do some testing, that would be nice.

This covers #80

[bemcdonnell]

@michaeltryby, I'm finally coming out of the stone ages ;-)

[bemcdonnell]

If you're interested here are some references:

http:https://stackoverflow.com/questions/7237133/create-string-buffer-throwing-error-typeerror-str-bytes-expected-instead-of-str

http:https://stackoverflow.com/questions/29578469/how-to-make-an-object-both-a-python2-and-python3-iterator

[goanpeca]

@bemcdonnell why 3.4? we should aim for either 3.5 or 3.6

[goanpeca]

The changes you made to utf8 encode are not robust enough if the plan is to support both python2.7 and 3. Take a look at six library and use that please.

[bemcdonnell]

@goanpeca, I updated the encoding behavior to use the python six module. Also, testing for 2.7, 3.4, 3.5, and 3.6 are all a pass! Let me know if you approve of these changes.

[goanpeca]

Hey @bemcdonnell looking much better

Still not sure about the next = __next__

[goanpeca]

Why do we need this?

[bemcdonnell]

So as I understand, the method __next__ was day lighted in Python 3 pep3114. In py2, by default, the iterator calls next() therefore, I had to add this line in order for it to step.

I could use the 2to3 package but that doesn't feel like progress to me. If you know of a better way, please enlighten me!

[goanpeca]

six.next(<iterator>) ?

[goanpeca]

I mean remove those redefinitions and use directly six.next does not that work?

[bemcdonnell]

I'm not having any success with your suggestion. This code porting guide shows the iterator next implementation as I have it above: Conservative Python 3 Porting Guide (see the end). Maybe there is still a better way?

[goanpeca]

Ok yes you are right :-)

[goanpeca]

@bemcdonnell we need to update the dependencies on setup.py to include six now.

[bemcdonnell]

@goanpeca, shall I merge?

[goanpeca]

yeah ;-)