Hi; For some reason my new build of Zope-2.4.1 didn't build certain files, including asyncore.py and asyncore.pyc (in ZServer/medusa). I'm suspecting the reason is because I have 2 versions of python running and in order to specify the latest I must type python2.1 at the command prompt. Is there some way to specify this version of python in the build, or does it look for this automatically, or am I missing something else? TIA, BenO
Ben, I recently built the same Zope version and also have 2 Python versions, 1.5.2 and 2.1 on RH Linux 7.1. "ls /usr/bin/py*" gave two instances of python - .../python1.5 and the other .../python2.1 Also there was a /usr/bin/python which was a copy (not symbolic link) of python1.5 So I overwrote that with a copy of python2.1 and the build went fine. I want the default python to be 2.1 anyway so I left it that way. -- Nitin Borwankar Ben Ocean wrote:
Hi; For some reason my new build of Zope-2.4.1 didn't build certain files, including asyncore.py and asyncore.pyc (in ZServer/medusa). I'm suspecting the reason is because I have 2 versions of python running and in order to specify the latest I must type python2.1 at the command prompt. Is there some way to specify this version of python in the build, or does it look for this automatically, or am I missing something else? TIA, BenO
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
On Sunday 16 September 2001 10:09, Nitin Borwankar wrote:
Ben,
I recently built the same Zope version and also have 2 Python versions, 1.5.2 and 2.1 on RH Linux 7.1. "ls /usr/bin/py*" gave two instances of python - .../python1.5 and the other .../python2.1 Also there was a /usr/bin/python which was a copy (not symbolic link) of python1.5 So I overwrote that with a copy of python2.1 and the build went fine. I want the default python to be 2.1 anyway so I left it that way.
Well, python was hard linked (not a copy of) to python1.5. You should have also had a python2 and a python2.1 (one is a hard link to the other). To compile zope with the right python just say either ... python2 pcgi.py or python2 wo_pcgi.py I suggest putting your python environment back together (i.e. hard linking python to python1.5 and hard linking python2 to python2.1). Then recompile zope with the above. -- Edward Muller - edwardam@home.com - edwardam@handhelds.org The way revolutions are completed is only by the death of the previous adherents to the paradigm
To compile zope with the right python just say either ...
python2 pcgi.py
or
python2 wo_pcgi.py
I needed to have MySQL support also and there appeared to be a "python ......" in one of the make scripts. So invoking python2 at the top level was not enough in my case, as part of the build would have the python==python1.5 invoked. I had to ensure that the "python" invocation would invoke python2.1. Is there any reason any more to keep around the 1.5 hard linked to python, rather than have 2.1 ? I was putting a fresh RH 7.1 and Zope 2.4 installation in place and had no legacy python code so I didn't bother. Nitin Borwankar.
I suggest putting your python environment back together (i.e. hard linking python to python1.5 and hard linking python2 to python2.1). Then recompile zope with the above.
-- Edward Muller - edwardam@home.com - edwardam@handhelds.org The way revolutions are completed is only by the death of the previous adherents to the paradigm
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
On Sun, 16 Sep 2001, Ben Ocean wrote:
Hi; For some reason my new build of Zope-2.4.1 didn't build certain files, including asyncore.py and asyncore.pyc (in ZServer/medusa). I'm suspecting the reason is because I have 2 versions of python running and in order to specify the latest I must type python2.1 at the command prompt. Is there some way to specify this version of python in the build, or does it look for this automatically, or am I missing something else? TIA, BenO
2.4.1 does not have an asyncore.py in ZServer/medusa anymore. Someone felt it was safe to use the asyncore.py coming with python 2.1. It is not! Your best bet for now is to copy asyncore.py from a 2.3.3 installation. Stefan
asyncore.py has been removed from the 2.4 distribution because it is now part of the standard Python distribution. There is no need to keep and maintain two different versions of a module. Andreas ----- Original Message ----- From: "Stefan H. Holek" <stefan@epy.co.at> To: "Ben Ocean" <zope@thewebsons.com> Cc: <zope@zope.org> Sent: Monday, September 17, 2001 05:10 Subject: Re: [Zope] Asyncore.py
On Sun, 16 Sep 2001, Ben Ocean wrote:
Hi; For some reason my new build of Zope-2.4.1 didn't build certain files, including asyncore.py and asyncore.pyc (in ZServer/medusa). I'm suspecting the reason is because I have 2 versions of python running and in order to specify the latest I must type python2.1 at the command prompt. Is there some way to specify this version of python in the build, or does it look for this automatically, or am I missing something else? TIA, BenO
2.4.1 does not have an asyncore.py in ZServer/medusa anymore. Someone felt it was safe to use the asyncore.py coming with python 2.1. It is not! Your best bet for now is to copy asyncore.py from a 2.3.3 installation.
Stefan
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
On Mon, 17 Sep 2001, Andreas Jung wrote:
asyncore.py has been removed from the 2.4 distribution because it is now part of the standard Python distribution. There is no need to keep and maintain two different versions of a module.
Point is they really *are* different ;) The one coming with Python is missing some vital parts. See: http://lists.zope.org/pipermail/zope-dev/2001-August/012866.html http://lists.zope.org/pipermail/zope-dev/2001-August/012869.html Stefan
I just installed the newest python and zope. I get this error when trying to build ZEO: [root@hermes Zope_software_home]# python lib/python/ZEO/start.py -p 8888 [root@hermes Zope_software_home]# Traceback (innermost last): File "lib/python/ZEO/start.py", line 268, in main import ZEO.StorageServer, asyncore File "lib/python/ZEO/__init__.py", line 86, in ? import fap File "lib/python/ZEO/fap.py", line 166, in ? fap() File "lib/python/ZEO/fap.py", line 127, in fap raise ImportError, 'Cannot import an up-to-date asyncore' ImportError: Cannot import an up-to-date asyncore *However*, here's a find: [root@hermes archive]# find / -name "asyncore.py" /apache/Python-2.1.1/Lib/asyncore.py /apache/ZopeInstallation/Zope_software_home/lib/python2.1/asyncore.py find: /proc/6/fd: Permission denied /usr/lib/python2.1/asyncore.py /usr/lib/python1.5/asyncore.py /usr/local/lib/python2.1/asyncore.py So, I'm more_than_a_little_confused as to what the heck's going on! Help!!! BenO At 03:43 PM 9/17/01 +0200, you wrote:
On Mon, 17 Sep 2001, Andreas Jung wrote:
asyncore.py has been removed from the 2.4 distribution because it is now part of the standard Python distribution. There is no need to keep and maintain two different versions of a module.
Point is they really *are* different ;) The one coming with Python is missing some vital parts. See:
http://lists.zope.org/pipermail/zope-dev/2001-August/012866.html http://lists.zope.org/pipermail/zope-dev/2001-August/012869.html
Stefan
participants (5)
-
Andreas Jung -
Ben Ocean -
Edward Muller -
Nitin Borwankar -
Stefan H. Holek