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

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.