support python 3.3+

[willkg]

steve should support Python 2.7 and 3.3+.

[AvdN]

As a first step: there are a few print statements in some of the .py files. We should changes those to function calls and include

from __future__ import print_function

at the top of all .py files (which gives you early detection by raising an error if you use a print statement instead of function in 2.7)

[willkg]

I've done a lot of this work before, so I know how I would go about doing it.

If you want to tackle this, then go for it. Otherwise I'm going to leave it because I think some of the other things @codersquid and I have been talking about are higher priority.

[AvdN]

Sorry, did not want to imply you did not know how to proceed with this. I should have just asked if it is ok for me to already insert the from __future__ import print_function.

I tend to debug (understand the code) with print statements and, after a long time still using print statements by default, I now finally naturally type print('some_variable:', some_variable) and that comes out as tuple in steve %-) every time. The rest has lower priority from my side as well.

[willkg]

No worries! I'm just trying to help by letting you know what I'm thinking priorities-wise.

I definitely want to add support for Python 3.3. richard supports it already amongst other things. I'm just saying that I personally won't be working on this right now because there are other things that have more impact on @codersquid's workflow.

Want me to assign this to you?

[AvdN]

Go ahead and assign.

[willkg]

I can't figure out how to assign you without dealing with github's user/group/permissions system. I'll deal with that later.

[AvdN]

No problem. Are you ever online at #richard ? I tried to setup IRC on irc.mozilla.org but I am not sure I am on the right channel

[willkg]

We hang out on IRC on Freenode in #richard. Looks like the README the wrong IRC information--I'll fix it now. Sorry about that!