blocks|key|90149|text|有几个选择...|type|unstyled|depth|inlineStyleRanges|entityRanges|data|90150|90151|如果这些模块将在Python2.6下运行，您可以简单地创建从2.6站点包目录到2.4站点包目录的符号链接。|ordered-list-item|90152|如果它们不能在2.6下运行，那么您可能需要在2.6下重新编译它们，或者安装它们的最新版本。只需确保在调用"python+setup.py"|offset|length|style|CODE|90153|时使用的是2.6版本|90154|..。|90155|如果你遇到其他挑战，你可能想把这篇文章发布到serverfault.com上。|90156|entityMap^0|0|0|0|1G|H|0|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|U|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|V|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|W|8|@$H|X|I|Y|J|K]]|9|@]|A|$]]|$1|L|3|M|5|6|7|Z|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|10|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|11|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|S|$]]

There are a couple of options...

<ol>
<li>If the modules will run under Python 2.6, you can simply create symbolic links to them from the 2.6 site-packages directory to the 2.4 site-packages directory.</li>
<li>If they will not run under 2.6, then you may need to re-compile them against 2.6, or install up-to-date versions of them. Just make sure you are using 2.6 when calling <code>"python setup.py"</code></li>
</ol>

...

You may want to post this on serverfault.com, if you run into additional challenges.

blocks|key|90174|text|它们并没有损坏，只是没有安装而已。解决方案是将它们安装在2.6版本下。但首先我们应该看看你是否真的应该这么做...|type|unstyled|depth|inlineStyleRanges|entityRanges|data|90175|是的，Python在安装时会将python命令替换为已安装的版本(除非您使用--alt-install运行它)。你没有确切地说出你的问题是什么，所以我来猜猜。您的问题是，许多使用Python的本地命令现在都失败了，因为它们在Python2.6中执行，而不是在Python2.4中执行。对吗？|90176|如果是这样，那么只需删除/usr/local/bin/python，并确保/usr/bin/python是指向/usr/bin/python2.4的符号链接。然后，您必须输入python2.6才能运行python2,6，但这是可以的。这是最好的方法。然后你只需要在2.6中安装你的所需要的包。|90177|但是如果我的猜测是错的，你真的需要在2.6版本下安装所有这些包，那么不要太担心。首先，安装setuptools。它包含一个easy_install脚本，然后可以使用以下命令安装模块|90178|easy_install+<modulename>|code-block|syntax|javascript|90179|它将从pypi.python.org下载该模块并进行安装。它还将安装任何依赖的模块。easy_install可以安装任何使用distutils作为安装程序的模块，这将使安装90%25的模块变得轻而易举。|90180|如果模块有一个C组件，它将编译它，然后你也需要库头，这将是更多的工作，你所能做的就是以标准的CentOS方式安装它们。|90181|您不应该在版本之间使用符号链接，因为库通常是针对特定版本的。对于2.4和2.6，我认为.pyc文件是兼容的(但我不是百分之百确定)，所以这可能会起作用，但任何使用C的模块都会崩溃。而其他版本的Python也会有不兼容的.pyc文件。我敢肯定，如果你这么做了，如果你这么做了，大多数Python人都不会帮你。;-)|90182|一般来说，我会尽量保持系统python的“整洁”，也就是说，我不会安装任何没有和打包工具一起安装的东西。相反，我使用virtualenv或buildout让每个应用程序都有自己的python路径，其中包含它的依赖项。因此，我的每个项目基本上都有自己的一组库。这样会变得更容易。|90183|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|10|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|11|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|12|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|13|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|14|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|V|$]]

They are not broken, they are simply not installed. The solution to that is to install them under 2.6. But first we should see if you really should do that...

Yes, Python will when installed replace the python command to the version installed (unless you run it with --alt-install). You don't exactly state what your problem is, so I'm going to guess. Your problem is that many local commands using Python now fail, because they get executed with Python 2.6, and not with Python 2.4. Is that correct?

If that is so, then simply delete /usr/local/bin/python, and make sure /usr/bin/python is a symbolic link to /usr/bin/python2.4. Then you would have to type python2.6 to run python2,6, but that's OK. That's the best way to do it. Then you only need to install the packages you need in 2.6.

But if my guess is wrong, and you really need to install all those packages under 2.6, then don't worry too much. First of all, install setuptools. It includes an easy_install script, and you can then install modules with 

<pre><code>easy_install &lt;modulename&gt;
</code></pre>

It will download the module from pypi.python.org and install it. And it will also install any module that is a dependency. easy_install can install any module that is using distutils as an installer, and not many don't. This will make installing 90% of those modules a breeze.

If the module has a C-component, it will compile it, and then you need the library headers too, and that will be more work, and all you can do there is install them the standard CentOS way.

You shouldn't use symbolic links between versions, because libraries are generally for a particular version. For 2.4 and 2.6 I think the .pyc files are compatible (but I'm not 100% sure), so that may work, but any module who uses C will break. And other versions of Python will have incompatible .pyc files as well. And I'm sure that if you do that, most Python people are not going to help you if you do it. ;-)

In general, I try too keep the system python "clean", I.e. I don't install anything there that isn't installed with the packaging tools. Instead I use virtualenv or buildout to let every application have their own python path where it's dependencies live. So every single project I have basically has it's own set of libraries. It gets easier that way.

blocks|key|91185|text|一些Python库可能仍然无法访问，因为在Python2.6中，site-packages被更改为dist-packages。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|91186|在这种情况下，唯一的方法是将站点包中生成的所有内容(例如由make+install生成)移动到dist包中，并创建一个sym-link。|91187|entityMap^0|W|D|1D|D|0|T|C|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|R|8|@]|D|@]|E|$]]]|I|$]]

Some Python libs may be still not accessible as with Python 2.6 <code>site-packages</code> is changed to <code>dist-packages</code>. 

The only way in that case is to do move all stuff generated in site-packages (e.g. by <code>make install</code>) to dist-packages and create a sym-link.

blocks|key|1055343|text|easy_install是一个很好的方法，但是有一些底层的方法来安装模块，只是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1055344|1055345|将模块源解压缩到某个目录|ordered-list-item|1055346|键入"python+setup.py+install"|1055347|1055348|当然，您应该使用所需的已安装python解释器版本来执行此操作；要检查它，请键入：|1055349|python+-V|1055350|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|P|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|Q|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|R|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|N|$]]

easy_install is good one but there are low level way for installing module, just:

<ol>
<li>unpack module source to some directory</li>
<li>type "python setup.py install"</li>
</ol>

Of course you should do this with required installed python interpreter version; for checking it type:

python -V

I have a problem of upgrading python from 2.4 to 2.6:
I have CentOS 5 (Full). It has python 2.4 living in /usr/lib/python2.4/ . Additional modules are living in /usr/lib/python2.4/site-packages/ . I've built python 2.6 from sources at /usr/local/lib/python2.6/ . I've set default python to python2.6 . Now old modules for 2.4 are out of pythonpath and are &quot;lost&quot;. In particular, yum is broken (&quot;no module named yum&quot;).
So what is the right way to migrate/install modules to python2.6?

Transition from Python2.4 to Python2.6 on CentOS, module migration problem

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我在将python从2.4升级到2.6时遇到了一个问题：我有CentOS 5 (Full)。它的python2.4位于/usr/lib/python2.4/中。其他模块位于/usr/lib/python2.4/site-package/中。我从/usr/local/lib/python2.6/上的源代码构建了pytho...

问在CentOS上从Python2.4到Python2.6的过渡，模块迁移问题
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在CentOS上从Python2.4到Python2.6的过渡，模块迁移问题EN