It's still a GIL. Python implementations without any GIL at all have been available for over a decade now. Python implementations that are much faster than CPython have been available for years.
(Almost) noone uses them, which clearly shows that nobody cares about performance or the GIL, so I hardly see them being a "killer feature". Killer features are something that people actually want.
The New GIL could be considered a killer feature of Python 3.2 if you use threading heavily. Integration of unladen swallow could also be considered a killer feature from a performance perspective.
In general, I think py3k already has enough features to warrant switching; what it doesn't have is broad library support. Most libraries have already started looking at the transition, but it is a good ways away. By the time 3.2 comes out a year from now, I expect most of the libraries I depend on to have made strong progress with compatibility, and that is what would make me switch.
3.2 is roughly a year away. By that time hopefully there will be some progress on switching to py3k, it also coincides with the two year "grace" period that was supposedly promised by Guido to some big projects. I don't think that there will be any single "killer" feature, and even if anyone would need it, I'd imagine unicode support would be much higher on priority ladder.
发布评论
评论（3）
它仍然是一个 GIL。 完全没有任何 GIL 的 Python 实现已经存在十多年了。比 CPython 快得多的 Python 实现已经存在多年了。
（几乎）没有人使用它们，这清楚地表明没有人关心性能或 GIL，所以我几乎不认为它们是一个“杀手级功能”。杀手级功能是人们真正想要的东西。
It's still a GIL. Python implementations without any GIL at all have been available for over a decade now. Python implementations that are much faster than CPython have been available for years.
(Almost) noone uses them, which clearly shows that nobody cares about performance or the GIL, so I hardly see them being a "killer feature". Killer features are something that people actually want.
如果您大量使用线程，New GIL 可以被认为是 Python 3.2 的杀手级功能。 空载燕子的集成也可以从性能角度来看，被认为是杀手级功能。
总的来说，我认为 py3k 已经有足够的功能来保证切换；它没有广泛的图书馆支持。大多数图书馆已经开始考虑这种转变，但这还有很长的路要走。到一年后 3.2 发布时，我预计我所依赖的大多数库都在兼容性方面取得了长足的进步，而这正是促使我进行切换的原因。
The New GIL could be considered a killer feature of Python 3.2 if you use threading heavily. Integration of unladen swallow could also be considered a killer feature from a performance perspective.
In general, I think py3k already has enough features to warrant switching; what it doesn't have is broad library support. Most libraries have already started looking at the transition, but it is a good ways away. By the time 3.2 comes out a year from now, I expect most of the libraries I depend on to have made strong progress with compatibility, and that is what would make me switch.
3.2 大约还有一年。到那时，希望在转向 py3k 方面能够取得一些进展，这也恰逢 Guido 向一些大型项目承诺的两年“宽限期”。我不认为会有任何单一的“杀手级”功能，即使有人需要它，我也认为 unicode 支持在优先级阶梯上会高得多。
3.2 is roughly a year away. By that time hopefully there will be some progress on switching to py3k, it also coincides with the two year "grace" period that was supposedly promised by Guido to some big projects. I don't think that there will be any single "killer" feature, and even if anyone would need it, I'd imagine unicode support would be much higher on priority ladder.