Followup fixes for python 3

[benson-basis]

• stop using future except in tests, use six instead
• fix py2 vs py3 issues with decode in setup.py, might fix windows. Might fix android.

[benson-basis]

Android succeeds at create with these changes.

[dessant]

We could avoid using six in setup.py, you could declare PY3 = sys.version_info >= (3,0,0) somewhere at the start and use that boolean for further checks.

[dessant]

It does fail for windows even with pyhon 2, but i think that is not caused by your code, I've tried to install an older commit and it is just as broken. I'll post some error logs regarding that, but the priority is android, linux and osx for now.

[akshayaurora]

future not needed anymore?

[akshayaurora]

@benson-basis thanks for this, could we remove future dependency all together? instead of using both future and six?

[benson-basis]

It's time-consuming to get all the 'future' out of the tests. I'll do it,
but I wanted to unblock things first.

On Wed, Nov 4, 2015 at 8:39 AM, Akshay Arora notifications@github.com
wrote:

@benson-basis https://github.com/benson-basis thanks for this, could we
remove future dependency all together? instead of using both future and six?

—
Reply to this email directly or view it on GitHub
#177 (comment).

[benson-basis]

@dessant I think this should solve everything mentioned except for adroid and getting rid of future from the tests. As noted elsewhere, I'm a bit stumped on the android side.

[inclement]

Thanks for the fixes. I've manually removed the apk stuff in the Makefile though as it's out of place (especially with the hardcoded machine-specific paths) - it would be better to add a test of some kind, or perhaps a pyjnius-specific test in p4a itself.

[benson-basis]

Thanks.

On Wed, Nov 4, 2015 at 5:47 PM, Alexander Taylor notifications@github.com
wrote:

Thanks for the fixes. I've manually removed the apk stuff in the Makefile
though as it's out of place (especially with the hardcoded machine-specific
paths) - it would be better to add a test of some kind, or perhaps a
pyjnius-specific test in p4a itself.

—
Reply to this email directly or view it on GitHub
#177 (comment).