Python 3 support

[elya5]

Although this causes some work, the long-term aim should be the support of python 3.

[tuffy]

Python 3 support is the biggest pending TODO item and I plan to start working on it further once Python Audio Tools 2.22 is finished starting with the C-based extension modules. I'd been holding off in the hope that Python 3 would ship with OS X at some point so that those users wouldn't have to do a separate install, but it's getting difficult to postpone the transition for much longer.

[elya5]

Wouldn't it be possible to create a version that supports python 2.x and 3.x at the same time. I know that other programs managed it to do that. See this answer on stackoverflow for example.
The problem is that this probably creates some code that is hard to understand afterwards.

[tuffy]

Migrating to code that supports both Python 2.7 and 3.x does seem like the most sensible solution in the near term. Urwid does the same thing by sticking to a portable subset of the language. But I'll definitely need to update the C code with #ifdefs to support Python 3's different way of defining extension modules, so that'll be my first priority.

[zet4]

Any update on this? Been over a year now...

[tuffy]

Python 2.7 and Python 3.3+ have been supported since version 3.0 which was released in December 2014.

[zet4]

This should probably be closed then? The project could use some readme file too.

[tuffy]

It probably should, yes. I'll try to build a reStructeredText README at some point, and maybe optimize it to be more github-friendly in general.