Switch to Python 3

[GoogleCodeExporter]

Tracshell just has PyYAML as a dependency, and 3.08 provides Python 3 support. 
Why not switch?

I've been wanting to use py3k for something else than tests for a while (my own 
code has 
dependencies which don't support py3k yet).

It's not as if tracshell was meant to be ran on servers, which might forced to 
use older versions of 
python.

Original issue reported on code.google.com by hsoft@hardcoded.net on 4 Apr 2009 at 2:38

[GoogleCodeExporter]

I haven't switched to py3k yet myself because the IO stuff is still in early
development and many of the core modules haven't been converted AFAIK.

You're welcome to create a tracshell-3k branch if you want to move ahead on 
this.

Original comment by j.kennet...@gmail.com on 15 Apr 2009 at 7:44

[GoogleCodeExporter]

First, I think that calling the IO system in py3k "early development" is far 
fetched. We're talking about an official 
release here (3.0), not a beta or alpha. The only problem with 3.0 is that the 
IO system is slow, but that's fixed in 
3.1 as it is re-written in C.

Even so, Tracshell does *not* need IO speed, so citing it as a reason not to 
use py3k is kind of weird.

As for the modules not being converted, I'm not too sure what you refer to. 3.0 
has been released quite a while 
ago, so it's not half-finished. The modules that have not been converted will 
never be converted, and those were 
old useless cruft.

This ticket is not about asking permission to create a py3k branch, it's about 
deciding if we would agree to move 
main development to py3k. It's useless to create a py3k branch if we don't move 
the development to it afterwards.

Original comment by hsoft@hardcoded.net on 16 Apr 2009 at 10:30

[GoogleCodeExporter]

I just hadn't switched yet was all I was getting at.

As of now I still haven't.

However, I think py3.1 is now bundled w/ most distro's now yeah? What about OS 
X / Windows (neither of which I bothered considering when I hacked this thing 
together originally)?

If it makes sense, it makes sense and I have no qualms. I just might need a few 
pointers on how to set up py3k/virtualenv on the same system to run alongside 
my 2.7 environment. :)

Original comment by j.kennet...@gmail.com on 17 Sep 2010 at 7:55

[GoogleCodeExporter]

Arch recently foisted py3k upon us, as good a time as any to try porting.

Hopefully it won't be too painful and we can stay Py 2.7 compatible.

Original comment by j.kennet...@gmail.com on 15 Dec 2010 at 4:15