search

AleksLitynski / teller

A game engine dedicated to making generative content easier to make.
1 stars 0 forks source link

why python 3.0 than 2.7? #15

Closed kyung01 closed 10 years ago

kyung01 commented 10 years ago

2.7 standards. 3.0 not yet standards. Stick with 2.7 if there is no good reason to use 3.0?

JoePrezioso commented 10 years ago

3.0 is what is on the lab computers, so it is what I've been using. I believe I also had issues using 2.7 syntax, as opposed to 3.0 syntax when trying to run my code.

kyung01 commented 10 years ago

from https://wiki.python.org/moin/Python2orPython3

"...However, there are some key issues that may require you to use Python 2 rather than Python 3.

Firstly, if you're deploying to an environment you don't control, that may impose a specific version, rather than allowing you a free selection from the available versions. Secondly, if you want to use a specific third party package or utility that doesn't yet have a released version that is compatible with Python 3, and porting that package is a non-trivial task, you may choose to use Python 2 in order to retain access to that package. Especially popular modules that don't yet support Python 3 include Twisted (for networking and other applications), gevent (a network library like Twisted, but using micro-threads rather than an explicitly asynchronous style)."

my visualizer codes does not work with Py3. I gotta check it one more time. If we do not want to use popular modules or other third party packages that are yet to support Py3 then it seems there is no problem with sticking with Py3.

However if we plan to use other third party libs then we ought to use Py2. For now current issue that we are having is just syntax and a function signature, which I do not perceive as good enough reason to stick to Py3 since the more experienced states to use Py2 for most cases.

Lets talk tomorrow. See what happens.

JoePrezioso commented 10 years ago

We're sticking with 2.7

/thread closed