When I first heard about UnladenSwallow I cheered. Then read that it was not targeting Python 3, and realized that this is really throwing a wrench into the works for Python 3.
I mean, switching to Py3k for the clean-ups and features is nice, but it's going to be hard for many to migrate if they've got to leave a 5x improvement in speed behind.
The people behind UnladenSwallow certainly must realize the repercussions for Python 3, no?
Yes, the Unladen Swallow people know that Py3k is the future. They also know that Google has a shit ton of Py2.X code that it's their job to make fast. That's why they're developing against Python2.X and then when it's time to merge back into CPython it will be merged in trunk (2.X) and then forward ported into Py3k.
I mean, switching to Py3k for the clean-ups and features is nice, but it's going to be hard for many to migrate if they've got to leave a 5x improvement in speed behind.
The people behind UnladenSwallow certainly must realize the repercussions for Python 3, no?