Python 2 vs Python 3

[dyladan]

We should decide early on if we're going with python 2 or 3. As the project sits right now, (17901c8), it is fully compatible with both runtimes. The Makefile is set up to use python 2 but it could be easily changed.

My opinion: Python 2 is what more python developers are going to know, but python 3 is the future of the language and is worth learning. Python 3 has some valuable runtime and library improvements, but the differences aren't going to matter much for our use case (we don't really much care about advanced algorithms for a simple project like this). I would say use python 3 just because it is worth learning, but if more people are comfortable with python 2 that would be fine also.

@cpgillem what are your thoughts on this since you seem to be leading this project?

edit: worth noting that ubuntu comes with python 2 as the default python

[MosesTroyer]

I vote for Python 3, the differences between the two aren't major, and as you said it's probably worth using the newer version of the language.

[cpgillem]

I think, since this is an educational club and this project is also meant to teach us as well as make a decent PLAN site, we could definitely do Python 3. This time Hardison isn't trying to throw something together with other administrative things on his mind. We actually have a few months of time to prepare.

That said, I'm asking stringy and mobyte, since stringy has given recommendations on this subject before, and mobyte, since he has already been working with Python 3 and virtualenvs on the Botler project. After we get their input let's make a decision.

[cpgillem]

I think the main thing to consider is third-party packages. I don't think we are really going to be using many, but it's something to consider.

[dyladan]

most of the major players have switched to python 3. Of those that haven't, there are alternatives. I've never had library issues with python 3. We need to just make a decision and stick with it.

[dyladan]

no matter what we thought we were going to do, i just tested the project and it fails on python3. This means either we have to start porting now (so we dont get too far down the rabbit hole) or just decide to go with python2

[dyladan]

@cpgillem should we just close this issue and stick with python 2 or do you want me to port our existing work to python 3?

[cpgillem]

How much work is porting it to Python 3? I think since this is a website that will be up long term and we still have a few months to make it, it might be worth looking into.

[dyladan]

i'll open up a branch and start working