Python 3000和“Python Regrets” [英] Python 3000 and "Python Regrets"

问题描述

我刚刚看到了2002年给出的Guido van Rossum''Python Regrets"
的幻灯片。它让我担心我的Python代码大部分都是
$如果他的所有想法都得到实施，b $ b就会被打破。他甚至不喜欢

''print''。当然，我没有资格与Van Rossum讨论关于Python方向的问题。


什么时候是Python" 3000"预计会出现？是否有与Python 2.3不兼容的预期

列表？严肃的Python程序员是否已经注意避免使用可能在Python 3000中消失的Python功能？

I just came across the slides for Guido van Rossum''s "Python Regrets"
talk, given in 2002. It worries me that much of my Python code would
be broken if all of his ideas were implemented. He doesn''t even like
''print''. Of course, I am not qualified to argue with Van Rossum about
the direction of Python.

When is Python "3000" expected to appear? Is there a list of expected
incompatibilities with Python 2.3? Are serious Python programmers
already taking care to avoid using Python features that may disappear
in Python 3000?

推荐答案

be*******@aol.com 写道：

我刚刚看到了2002年给出的Guido van Rossum''Python Regrets"
讲话的幻灯片。它让我担心如果所有的话我的Python代码都会被破坏他的想法得到了实施。他甚至不喜欢打印''。当然，我没有资格与范罗森谈论Python的方向。

什么时候是Python" 3000"预计会出现？是否有与Python 2.3预期不兼容的列表？严肃的Python程序员是否已经注意避免使用可能在Python 3000中消失的Python功能？

I just came across the slides for Guido van Rossum''s "Python Regrets"
talk, given in 2002. It worries me that much of my Python code would
be broken if all of his ideas were implemented. He doesn''t even like
''print''. Of course, I am not qualified to argue with Van Rossum about
the direction of Python.

When is Python "3000" expected to appear? Is there a list of expected
incompatibilities with Python 2.3? Are serious Python programmers
already taking care to avoid using Python features that may disappear
in Python 3000?

Python 3000有点想象。这是假设：如果Guido能够做什么他们想做什么而不用担心向后兼容会怎么样？


Python 3000和Python 3.0是同样的事情（或者同一个计划的b $ b $ - 既没有实施也没有全面计划）。

现在它们是不同的想法 - 如果你看到引用Python 3.0，它它还包括一些向后不兼容的变化和清理，比如可能

input（）会消失，整数除法会消失，而且事情

like range（）将返回迭代器（并且xrange消失）。但它更加保守，并且作为一个更现实的计划呈现出来。打印

仍然存在。


-

Ian Bicking / ia ** @ colorstudy.com / http：//blog.ianbicking .org

Python 3000 is kind of imaginary. It''s a what-if: what if Guido could
do whatever he wanted without worrying about backward compatibility?

At one point Python 3000 and Python 3.0 were kind of the same thing (or
the same plan -- neither are implemented or even thoroughly planned).
Now they are separate ideas -- if you see references to Python 3.0, it
also includes some backward incompatible changes and cleanup, like maybe
input() will disappear, and integer division will go away, and things
like range() will return iterators (and xrange goes away). But it''s
much more conservative, and presented as a more realistic plan. print
will still be around.

--
Ian Bicking / ia**@colorstudy.com / http://blog.ianbicking.org

[be ******* @ aol.com]

[be*******@aol.com]

我刚看到幻灯片Guido van Rossum'的Python
遗憾在2002年给出的谈话。令我担心的是，如果他的所有想法都得到实施，我的大部分Python代码都将被破坏。


实际上，如果你不改变你使用的Python

实现，它们都不会破坏。

他甚至不喜欢''打印''。当然，我没有资格与范罗森谈论Python的方向。

什么时候是Python" 3000"预计会出现？


这通常表示为从地狱

冻结的时间开始的正偏移，但人们对这两个部分的估计有所不同。最低价格为
，要求Guido首先得到一份工作，他可以​​专注于Python开发。当地狱冻结过来时会发生这种情况，但可能会在此之前发生。很难说。

是否有与Python 2.3预期不兼容的列表？


No.

严肃的Python程序员是否已经注意避免使用可能在Python 3000中消失的Python功能？

I just came across the slides for Guido van Rossum''s "Python
Regrets" talk, given in 2002. It worries me that much of my Python
code would be broken if all of his ideas were implemented.
Actually, none of it would break, provided you don''t change the Python
implementation you use.
He doesn''t even like ''print''. Of course, I am not qualified to argue
with Van Rossum about the direction of Python.

When is Python "3000" expected to appear?
This is usually expressed an as a positive offset from the time hell
freezes over, but people vary in their estimation of both parts. At a
minimum, it requires that Guido first get a job where he can
concentrate on Python development. That will happen when hell freezes
over, but may happen before then. Hard to say.
Is there a list of expected incompatibilities with Python 2.3?
No.
Are serious Python programmers already taking care to avoid
using Python features that may disappear in Python 3000?

不，虽然有些人自然会避免可疑的功能而不会受到威胁< wink> ;.

No, although some naturally avoid dubious features without being
threatened <wink>.

无论如何，有什么值得担心的？当时间到来的时候，只需要将一个将Python 1.6（或任何你喜欢的东西）转换成Python3K的小b / b $ b脚本;它将只需要七行P3K代码。

Anyway, what''s to worry about? When the time comes just whip out a little
script that converts Python 1.6 (or whatever you like) to Python3K; it will
only take seven lines of P3K code.

这篇关于Python 3000和“Python Regrets”的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！