Archlinux:Plan for python upgrade

[hubert_star]

Hi everybody,

Python-2.6 is out and Python-3.0 is scheduled for release in a couple of
weeks. People have been asking how I am going to handle the update so I
thought I'd post a summary here.

There are packages that need rebuilt not matter how I handle the
upgrade. I know of 39 packages in [extra] which link to
libpython2.5.so. Also 8 packages add their path to the python system
path and it is easier to rebuild them than hack some backwards
compatibility.

My current plan is that the python package will be python3.0 and add a
python2 package for python2.6. This bring in a couple of issues.
Everything that (make)depends on python will need changed to python2 (48
packages). More difficult is that package with "/usr/bin/python" or
"/usr/bin/env python" in their scripts need this fixed (addition 30
rebuilds and effects many of the above rebuilds). Some of these
packages are nice and just require a rebuild and their scripts point in
the right place. Others require a bit of sed magic.

This plan requires a total of 125(!) rebuilds but most of the are fairly
simple to transition to python2. Of the 33 packages on my system, the
only package I have had trouble rebuilding so far is subversion as
autoreconf calls something that calls python but I have not looked into
it too hard or even checked if it as actually a problem...

The backup plan is to keep the python as the python-2 series and add a
python3 package. This means less rebuilds at the moment but this will
make transitioning packages to python3 harder (requiring the sed magic
for scripts to point at python3 instead of python). Also, I personally
think this is the less clean approach long term. But, if people feel
strongly that this is the best route to go, I may be convinced (it is a
lot less work at my end).

Both the gnome and boost rebuilds need to be moved from [testing] before
I start this due to overlapping packages with the python rebuilds.

Cheers,
Allan

转载自archlinux新闻组

看来python3进入系统已经指日可待了

[karron]

疯掉了... python3和python2是不完全兼容的. 贸然升级, 可能有些软件会不能正常使用.

[hubert_star]

可以说，整个GUI 2/3的软件都要重新调整来过

[karron]

我只能说arch真猛. 或者说, 以后一段时间里面, arch的用户可能会有点惨. 不过也许会一直呆在testing里面吧.

[windwiny]

arch就是快 强

[hubert_star]

应该在testing里很长一段时间，不会贸然进extra的，其实archlinux不加testing问题很少，很稳定

[HuntXu]

有点吓人，估计也要像kdemod那样搞个legacy并存一段时间吧...

还好机器上没很多依赖python的程序...ooo-devel,vim/gvim还有emesene而已...

[karron]

有点吓人，估计也要像kdemod那样搞个legacy并存一段时间吧...

还好机器上没很多依赖python的程序...ooo-devel,vim/gvim还有emesene而已...

有很多重要的但是你平时不会注意的软件都是python写的.

[yysq009]

该来的，迟早要来的！

[jarryson]

脚本语言应该比其他的要好很多。绝对不会有类似qt3到qt4那样的。

qt3到qt4的时候怎么就没有人说什么呢

[karron]

ls, 你要搞明白的是, 我们并没有讨论语言本身的升级. 而是arch现在要将python3作为默认的python, 这个可能会导致很多软件无法正常运行. qt3, qt4, 本身只是运行库, 无所谓什么默认, 只要安装了相应的库, 使用qt3的软件跟使用qt4的软件都是互不影响的. 而python是解释语言, 这个问题就严重得多, 所有的python脚本必须通过python来运行, 而本身python2和python3并不完全兼容, 所以, 遇到的问题远比qt3, qt4严重. 说实在的. qt3, qt4本身就是可以共存, 并不会有什么问题.

[jarryson]

一样的，qt4和qt3程序不兼容是肯定的，虽然可以共存，不过我是不想存在两种qt的。但是python程序也许还兼容，只是可能需要小幅度修改，个人感觉比gcc，qt更新要好的多。也许是我不清楚到底python3比2.6改变多少接口。想别人python开发者不会没有想到这点，所以就算作为默认的python也没有关系，不可能停滞不前的。

[asluozijun]

自己可以装一个 python2.7x
....

[JiangHui]

自杀的来挖坟……

[susbarbatus]

原来是坟