Question: Should we go to Python 3?

[Bruce Frederiksen]

OK, when this question came up before wxpython had no definite plans for Python 3, so we were stuck with Python 2.

Now we should be free (as far as I can tell) to move to Python 3.  The benefits that I see are:

1. All strings are unicode, so if we want this to be international friendly, it would be easier in Python 3.
2. A chance to learn Python 3.
3. If the project lives more than two or three years, we will be porting to Python 3 someday anyway.

The drawback would be that it can be a little confusing switching back and forth between 2 and 3 (85% of the problem being the print statement/function change) for those of us still stuck on 2 for other reasons (e.g., Django).  But I found myself getting somewhat acclimated to switching on the Pyke project.

What do you think?

-Bruce

[Jason Keene]

I have yet to do anything with Python 3.  It might be a good learning experience.

--
You received this message because you are subscribed to the Google Groups "Tampa Bay Python AVR" group.
To post to this group, send email to tampa-bay-...@googlegroups.com.
To unsubscribe from this group, send email to tampa-bay-python...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/tampa-bay-python-avr?hl=en.

[RODNEY DRENTH]

My thinking is that this is the year that everyone will be pushing to move to Python 3.

I figure that even though there still are a lot of apps in Python 2, If we look down the road

a couple of years, Python 3 will be more prevalent. We're going to have to deal with Python 2

Python 3 confusion sometime, now's a good of time as any.

 

Rodney Drenth

--