发布了Python 2.6a1和3.0a3 [英] RELEASED Python 2.6a1 and 3.0a3
问题描述
----- BEGIN PGP签名消息-----
哈希：SHA1
代表Python开发团队和Python社区，我很高兴宣布推出Python 2.6的第一个alpha版本，以及Python 3.0的第三个
alpha版本。
Python 2.6不仅是Python 2系列的下一个进步，它还是一个过渡版本，帮助开发人员开始准备他们的Python代码3.0。因此，许多功能都是从Python 3.0反向移植到2.6。同时发布两个版本的b / b版本是有意义的，使用Python 1.6和2.0版本将其优先级设置为
。
在alpha测试周期中，我们将在每月发布周期中发布两个版本的
锁步。发布将在每个月的最后一个星期五发生在
。如果这个时间表运作良好，我们将在测试计划期间继续以锁定的方式发布
。有关计划详情，请参阅PEP 361
：
http://www.python.org/dev/peps/pep-0361/
，但仍然存在一些已知的问题和
功能集还没有最终确定。发布这些alpha版本是为了征求反馈并希望发现错误，以及
允许您确定2.6和3.0中的更改可能会如何影响
$ b你好吗？如果您发现内容有问题或不正确，请提交错误
报告
http://bugs.python.org
欲了解更多信息和可下载的发行版，请参阅Python
2.6网站
网站：
http://www.python.org/download/releases/2.6/
和Python 3.0网站：
< a rel =nofollowhref =http://www.python.org/download/releases/3.0/\"target =_ blank> http://www.python.org/download/releases/3.0/
我们正在计划一些额外的alpha版本，最终的
发布时间表仍有待确定。
享受，
- -Barry
巴里华沙
ba *** @ python.org
Python 2.6 / 3.0发布经理
（代表en轮胎python-dev团队）
----- BEGIN PGP SIGNATURE -----
版本：GnuPG v1.4.8（达尔文）
iQCVAwUBR8mlu3EjvBPtnXfVAQKePAQAgx6w9wztfJaSWkbKrb wur2U6t6o5aIY5
pyMa00CZWY06p8099BztcSjgp5rKrd6 / 9V7cJ0NP7NLZ + tz20uRfyI8uqoIYBIWC
ibJay6SSnzgOQM3PRIJV / K / m0dVPPPVD1LDnoEvuu + cKUpV434yHdgWkMPswsxUd
fLydrXABlOM =
= l6aj
----- END PGP SIGNATURE -----
< blockquote> On 1 Mrz。，19：51，Barry Warsaw< ba ... @ python.orgwrote：
Python 2.6不仅是下一个进步Python 2系列，它也是一个过渡版本，帮助开发人员开始准备他们的Python 3.0代码。
这不是一个愚蠢的想法吗？人们必须首先从2.5或更低的
版本迁移到Python 2.6才能迁移到Python 3.0？什么是
阻止直接从
2.5到3.0迁移的固有/技术原因？
Kay Schluehr< ka ********** @ gmx.netwrites：
On 1 Mrz。，19：51，Barry Warsaw< ba ... @ python.orgwrote：
Python 2.6不仅是Python 2系列的下一个进步，它还是
也是一个过渡版本，帮助开发人员开始准备他们的Python 3.0代码。
这不是一个愚蠢的想法吗？人们必须首先从2.5或更低的
版本迁移到Python 2.6才能迁移到Python 3.0？什么是
阻止从
2.5到3.0直接迁移的固有/技术原因？
迁移的既定目标之一是''2to3''程序
只会迁移Python 2.6代码-Python 3.0码。所以，
最流畅的迁移路径将是：
*让您的程序使用Python 2.6;然后
*使用''2to3''自动翻译该程序以使用
Python 3.0;然后
*为该程序停止使用Python 2.x，仅使用Python 3.x.
另一个原因是来自Python 3.0很可能会向Python 2.6.x提供backported（如果可能的话），但不会更新到任何早期的
版本。
-
\爸爸一直认为笑是最好的药，我猜这是为什么我们几个人死于肺结核。 - 杰克|
_o__）Handey |
Ben Finney
" ; Kay Schluehr < ka ********** @ gmx.netwrote in message
news：eb ******************** ************** @ c33g2000 hsd.googlegroups.com ...
| 1先生，19：51，Barry Warsaw< ba ... @ python.orgwrote：
|
| Python 2.6不仅是Python 2系列的下一个进步，它还是
|也是一个过渡版本，帮助开发人员开始准备
|他们的Python 3.0代码。
|
|这不是一个愚蠢的想法吗？人们必须从2.5或更低版本迁移
|发布到Python 2.6首先只是为了迁移到Python 3.0？
你可以随意更新你想要的任何代码。 Barry刚才说2.6
将有助于简化流程。 （至少对于那些需要增量更改的人来说，这应该是一次性完成所有操作。）在任何情况下，2.5和
之前的代码不依赖于以后的错误固定应该通常运行
不变的2.6
|什么是
|防止直接迁移的固有/技术原因
| 2.5到3.0？
无。
tjr
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On behalf of the Python development team and the Python community, I''m
happy to announce the first alpha release of Python 2.6, and the third
alpha release of Python 3.0.
Python 2.6 is not only the next advancement in the Python 2 series, it
is also a transitionary release, helping developers begin to prepare
their code for Python 3.0. As such, many features are being
backported from Python 3.0 to 2.6. It makes sense to release both
versions in at the same time, the precedence for this having been set
with the Python 1.6 and 2.0 releases.
During the alpha testing cycle we will be releasing both versions in
lockstep, on a monthly release cycle. The releases will happen on the
last Friday of every month. If this schedule works well, we will
continue releasing in lockstep during the beta program. See PEP 361
for schedule details:
http://www.python.org/dev/peps/pep-0361/
Please note that these are alpha releases, and as such are not
suitable for production environments. We continue to strive for a
high degree of quality, but there are still some known problems and
the feature sets have not been finalized. These alphas are being
released to solicit feedback and hopefully discover bugs, as well as
allowing you to determine how changes in 2.6 and 3.0 might impact
you. If you find things broken or incorrect, please submit a bug
report at
http://bugs.python.org
For more information and downloadable distributions, see the Python
2.6 web
site:
http://www.python.org/download/releases/2.6/
and the Python 3.0 web site:
http://www.python.org/download/releases/3.0/
We are planning a number of additional alpha releases, with the final
release schedule still to be determined.
Enjoy,
- -Barry
Barry Warsaw
ba***@python.org
Python 2.6/3.0 Release Manager
(on behalf of the entire python-dev team)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
iQCVAwUBR8mlu3EjvBPtnXfVAQKePAQAgx6w9wztfJaSWkbKrb wur2U6t6o5aIY5
pyMa00CZWY06p8099BztcSjgp5rKrd6/9V7cJ0NP7NLZ+tz20uRfyI8uqoIYBIWC
ibJay6SSnzgOQM3PRIJV/K/m0dVPPPVD1LDnoEvuu+cKUpV434yHdgWkMPswsxUd
fLydrXABlOM=
=l6aj
-----END PGP SIGNATURE-----
On 1 Mrz., 19:51, Barry Warsaw <ba...@python.orgwrote:
Python 2.6 is not only the next advancement in the Python 2 series, it
is also a transitionary release, helping developers begin to prepare
their code for Python 3.0.Isn''t this a silly idea? People have to migrate from 2.5 or lower
releases to Python 2.6 first just to migrate to Python 3.0? What are
the inherent / technical reasons that prevent migration directly from
2.5 to 3.0?
Kay Schluehr <ka**********@gmx.netwrites:
On 1 Mrz., 19:51, Barry Warsaw <ba...@python.orgwrote:
Python 2.6 is not only the next advancement in the Python 2 series, it
is also a transitionary release, helping developers begin to prepare
their code for Python 3.0.
Isn''t this a silly idea? People have to migrate from 2.5 or lower
releases to Python 2.6 first just to migrate to Python 3.0? What are
the inherent / technical reasons that prevent migration directly from
2.5 to 3.0?One of the stated goals of the migration is that the ''2to3'' program
will only migrate Python 2.6 code -Python 3.0 code. So, the
smoothest migration path will be:
* get your program working with Python 2.6; then
* use ''2to3'' to automatically translate that program to work with
Python 3.0; then
* stop using Python 2.x for that program, only use Python 3.x.
Another reason is that good features from Python 3.0 will likely be
backported (if possible) to Python 2.6.x, but not to any earlier
version.
--
\ "Dad always thought laughter was the best medicine, which I |
`\ guess is why several of us died of tuberculosis." -- Jack |
_o__) Handey |
Ben Finney
"Kay Schluehr" <ka**********@gmx.netwrote in message
news:eb**********************************@c33g2000 hsd.googlegroups.com...
| On 1 Mrz., 19:51, Barry Warsaw <ba...@python.orgwrote:
|
| Python 2.6 is not only the next advancement in the Python 2 series, it
| is also a transitionary release, helping developers begin to prepare
| their code for Python 3.0.
|
| Isn''t this a silly idea? People have to migrate from 2.5 or lower
| releases to Python 2.6 first just to migrate to Python 3.0?
You are quite free to update any code you want. Barry just said that 2.6
will help make the process easier. (At least it should for people who
prefer incremental changes to doing it all at once.) In any case, 2.5 and
earlier code that does not depend on bugs later fixed should usually run
unchanged in 2.6
| What are
| the inherent / technical reasons that prevent migration directly from
| 2.5 to 3.0?
None.
tjr
这篇关于发布了Python 2.6a1和3.0a3的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
