python 3.0
December 10th, 2008
James Bennett: Python 3.0 was designed to clear up a lot of now-inertial legacy issues with the Python language and figure out good ways to do things now instead of unquestioningly sticking with what seemed like good ways (or, more often, the least painful ways) to do things five or ten years ago. (via Michael Tsai)
Although I do not look forward to porting all the code we have from python 2.5 to python 3.0, I very much look forward to python 3.0 when we get there.
Airfoil
Audio Hijack Pro
Fission
Nicecast
Piezo
Pulsar
December 11th, 2008 at 4:10 am
Python 2.6 provides incompatibility warnings for code that is expected to break with Python 3.0. You can get most of the porting work done if you use Python 2.6.
December 11th, 2008 at 8:12 am
Out of interest, how much Python code do you guys have in your OS X apps?
December 11th, 2008 at 2:25 pm
Paul – Currently none, although we are starting to play with PyObjc and will eventually be shipping a bit to see how it fairs in the wild. We have a fair amount of python running on the website, and another large chunk running our build system.
December 12th, 2008 at 12:55 pm
Nice site!
December 12th, 2008 at 11:35 pm
Gotcha, thanks for the insight.